Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
3bbbf18a
Commit
3bbbf18a
authored
Jun 06, 2009
by
Antoine Pitrou
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add what's new entry for r73236.
parent
c0d98aa5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
18 additions
and
0 deletions
+18
-0
Doc/whatsnew/3.1.rst
Doc/whatsnew/3.1.rst
+18
-0
No files found.
Doc/whatsnew/3.1.rst
View file @
3bbbf18a
...
...
@@ -384,6 +384,24 @@ New, Improved, and Deprecated Modules
(Contributed by Brett Cannon.)
* :mod:`pickle` is now more compatible with Python 2.x when using a
2.x-compatible protocol (that is, protocol 2 or lower), through translation
of some standard library module names to or from their Python 2.x
equivalents.
This means that more (protocol 2 or lower) pickles produced by Python 3.1
will be reusable by Python 2.x, and vice-versa. Standard set objects are
an example of this improvement.
This has the (unfortunate but unavoidable) side effect that some
protocol 2 pickles produced by Python 3.1 won't be readable with
Python 3.0. The latest pickle protocol, protocol 3, should be used when
migrating data between Python 3.x implementations, as it doesn't attempt
to remain compatible with Python 2.x.
(Contributed by Alexandre Vassalotti and Antoine Pitrou, :issue:`6137`.)
Optimizations
=============
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment