[Python-ideas] Was `os.errno` undocumented?

Nick Coghlan ncoghlan at gmail.com
Tue May 29 09:07:36 EDT 2018


On 29 May 2018 at 20:06, Petr Viktorin <encukou at gmail.com> wrote:

> Is that reasoning sound?
> Should our policy on removing internal imports take that into account?
>

As Steven noted, the normative answer to this is in PEP 8:
https://www.python.org/dev/peps/pep-0008/#public-and-internal-interfaces

Since `os.errno` is a transitive import, is not included in `os.__all__`,
and isn't documented in the library reference, it's considered an
implementation detail that can be removed without a deprecation period.

That said, it should still be mentioned in the "Porting to Python 3.7"
section of the What's New guide, with the fix being to switch to "import
errno" in any affected code.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20180529/70105ebf/attachment.html>


More information about the Python-ideas mailing list