[Python-Dev] Documentation strategy for PEP 3151

[Brian Curtin]

On Wed, Oct 12, 2011 at 09:17, Antoine Pitrou <solipsis at pitrou.net> wrote:
>
> Hello,
>
> I'd like some advice on what the best path is in cases such as:
>
>   A :exc:`socket.error` is raised for errors from the call
>   to :func:`inet_ntop`.
>
> Should I replace "socket.error" with "OSError" (knowing that the
> former is now an alias of the latter), or leave "socket.error" so that
> people have less surprises when running their code with a previous
> Python version?

I would expect the 3.3 documentation shows the best way to write 3.3
code, so I'd prefer to see OSError there.

A good "What's New" entry as well as explanation/example of how the
hierarchy has changed in library/exceptions.rst should cover anyone
questioning the departure from socket.error.