whatsnew: __complex__ may not return float, .so may have multiple python modules

Also a NEWS wording fixup.
This commit is contained in:
R David Murray 2014-02-11 08:13:10 -05:00
parent eb74876e99
commit 801fe934d9
2 changed files with 12 additions and 3 deletions

View File

@ -1443,6 +1443,10 @@ Other Improvements
values for its constants from the C header files, instead of having the
values hard-coded in the python module as was previously the case.
* Loading multiple python modules from a single OS module (``.so``, ``.dll``)
now works correctly (previously it silently returned the first python
module in the file). (Contributed by Václav Šmilauer in :issue:`16421`.)
Significant Optimizations
@ -1725,6 +1729,11 @@ Changes in the Python API
:exc:`ValueError` if given a negative length; previously it returned nonsense
values (:issue:`14794`).
* The :class:`complex` constructor, unlike the :mod:`cmath` functions, was
incorrectly accepting :class:`float` values if an object's ``__complex__``
special method returned one. This now raises a :exc:`TypeError`.
(:issue:`16290`.)
Changes in the C API
--------------------

View File

@ -2262,10 +2262,10 @@ Core and Builtins
builtins.
- Issue #16455: On FreeBSD and Solaris, if the locale is C, the
ASCII/surrogateescape codec is now used, instead of the locale encoding, to
ASCII/surrogateescape codec is now used (instead of the locale encoding) to
decode the command line arguments. This change fixes inconsistencies with
os.fsencode() and os.fsdecode() because these operating systems announces an
ASCII locale encoding, whereas the ISO-8859-1 encoding is used in practice.
os.fsencode() and os.fsdecode(), because these operating systems announce an
ASCII locale encoding, but actually use the ISO-8859-1 encoding in practice.
- Issue #16562: Optimize dict equality testing. Patch by Serhiy Storchaka.