A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2011-October/114038.html below:

[Python-Dev] Documentation strategy for PEP 3151

[Python-Dev] Documentation strategy for PEP 3151 [Python-Dev] Documentation strategy for PEP 3151Benjamin Peterson benjamin at python.org
Wed Oct 12 16:24:59 CEST 2011
2011/10/12 Antoine Pitrou <solipsis at pitrou.net>:
>
> 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 think you should say OSError but leave a historical note with a
versionchanged on it.



-- 
Regards,
Benjamin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4