mirrors/cpython
0
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2024-11-30 13:24:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

whatsnew: os.path.samestat on windows, keyword defaults evaluation order.

Browse Source
This commit is contained in:
R David Murray 2014-02-12 00:02:34 -05:00
parent db2d8a4ca5
commit 2167e29d31
2 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Doc/library/os.path.rst
View File

@ -251,7 +251,7 @@ the :mod:`glob` module.)
.. function:: samefile(path1, path2)
Return ``True`` if both pathname arguments refer to the same file or directory.
On Unix, this is determined by the device number and i-node number and raises an
This is determined by the device number and i-node number and raises an
exception if a :func:`os.stat` call on either pathname fails.
Availability: Unix, Windows.

12
Doc/whatsnew/3.4.rst
View File

@ -955,6 +955,10 @@ the :func:`multiprocessing.cpu_count` function (which is now implemented in
terms of the new :mod:`os` function). (Contributed by Trent Nelson, Yogesh
Chaudhari, Victor Stinner, and Charles-François Natali in :issue:`17914`.)
:func:`os.path.samestat` is now available on the Windows platform (and the
:func:`os.path.samefile` implementation is now shared between Unix and
Windows). (Contributed by Brian Curtin in :issue:`11939`.)
pdb
---
@ -1752,9 +1756,13 @@ Changes in the Python API
special method returned one. This now raises a :exc:`TypeError`.
(:issue:`16290`.)
* The :class:`int` constructor in 3.2 and 3.3 erroneously accept :class:`float`
* The :class:`int` constructor in 3.2 and 3.3 erroneously accepts :class:`float`
values for the *base* parameter. It is unlikely anyone was doing this, but
if so, it will now raise a :exc:`TypeError` (:issue:`16772`).
if so, it will now raise a :exc:`TypeError` (:issue:`16772`).
* Defaults for keyword-only arguments are now evaluated *after* defaults for
regular keyword arguments, instead of before. Hopefully no one wrote any
code that depends on the previous buggy behavior (:issue:`16967`).
Changes in the C API