[docs] [issue33666] os.errno gone AWOL
report at bugs.python.org
Mon May 28 10:29:44 EDT 2018
Petr Viktorin <encukou at gmail.com> added the comment:
I think this was closed prematurely.
> Projects that depend on it are incorrect and should be fixed.
That's definitely correct; no one here is arguing against it.
However, there are projects out there depending on it -- it worked since around Python 2.5, and is readily available in `os.` tab completion.
I think that documenting the removal would be good for our users.
Furthermore, not all of its uses can be fixed. I've seen it printed in books. There are many answers/guides/tutorials around mentioning os.errno, for example:
... and people tend based their code on such recipes, rather than checking what's documented.
And, of course, projects run into this:
resolution: not a bug ->
status: closed -> open
Python tracker <report at bugs.python.org>
More information about the docs