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