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
326c57d1
Commit
326c57d1
authored
Nov 26, 2010
by
Georg Brandl
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Typo fix.
parent
62f52c48
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
Doc/whatsnew/3.2.rst
Doc/whatsnew/3.2.rst
+2
-2
No files found.
Doc/whatsnew/3.2.rst
View file @
326c57d1
...
...
@@ -657,7 +657,7 @@ The :mod:`os` module has two new functions: :func:`~os.fsencode` and
:data:`os.environ`, :func:`os.getenvb` function and
:data:`os.supports_bytes_environ` constant.
``'mbcs'`` encoding doesn't ignore the error handler argument anymore. By
``'mbcs'`` encoding doesn't ignore the error handler argument any
more. By
default (strict mode), it raises an UnicodeDecodeError on undecodable byte
sequence and UnicodeEncodeError on unencodable character. To get the ``'mbcs'``
encoding of Python 3.1, use ``'ignore'`` error handler to decode and
...
...
@@ -721,7 +721,7 @@ require changes to your code:
* The :mod:`nntplib` module was reworked extensively, meaning that its APIs
are often incompatible with the 3.1 APIs.
* :class:`bytearray` objects cannot be used anymore as filenames: convert them
* :class:`bytearray` objects cannot be used any
more as filenames: convert them
to :class:`bytes`.
* PyArg_Parse*() functions:
...
...
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