From 96e05b3e65f81646401e89f76d7b1a2213783463 Mon Sep 17 00:00:00 2001 From: Antoine Pitrou Date: Tue, 10 May 2011 17:20:17 +0200 Subject: [PATCH] Update with URL of hg repo --- pep-3151.txt | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/pep-3151.txt b/pep-3151.txt index d32225099..dd2e47b0e 100644 --- a/pep-3151.txt +++ b/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