iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update with URL of hg repo

This commit is contained in:
Antoine Pitrou 2011-05-10 17:20:17 +02:00
parent 110a307f5f
commit 96e05b3e65
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
pep-3151.txt
View File

@ -504,15 +504,16 @@ chance to be accepted for Python 3.2.
Implementation Implementation
============== ==============
A reference implementation has been started in ``branches/pep-3151`` in the A reference implementation has been started in
Python SVN repository. For now only `Step 1`_ is implemented, and without http://hg.python.org/features/pep-3151/ in branch ``pep-3151``.
the deprecation warnings. However, it shows that coalescing the exception For now only `Step 1`_ is implemented, and without the deprecation warnings.
types doesn't produce any significant annoyance in the standard library. However, it shows that coalescing the exception types doesn't produce any
The only observed trouble is with the respective constructors of ``IOError`` significant annoyance in the standard library. The only observed trouble
and ``WindowsError``, which are slightly incompatible. The way it is solved is with the respective constructors of ``IOError`` and ``WindowsError``,
is by keeping the ``IOError`` semantics and adding a fourth optional argument which are slightly incompatible. The way it is solved is by keeping the
to allow passing the Windows error code (which is different from the POSIX ``IOError`` semantics and adding a fourth optional argument to allow passing
errno). All ``PyErr_SetFromWindowsErr*`` functions still do the right thing. the Windows error code (which is different from the POSIX errno). All
``PyErr_SetFromWindowsErr*`` functions do the right thing.
Possible alternative Possible alternative