[issue33666] os.errno gone AWOL

Serhiy Storchaka added the comment: If document disappearing of os.errno, we should document disappearing of all other names in other modules in all versions. It is possible to write a script that outputs dir(mod) for all modules and compare results between different Python versions. Are you

[issue33666] os.errno gone AWOL

Miro Hrončok added the comment: I can document this, yes. I've opened this issue so I could prep a PR. -- ___ Python tracker ___ ___

[issue33666] os.errno gone AWOL

STINNER Victor added the comment: > os.errno as well as os.sys or os.abc is an implementation detail. I agree but... > It can be changed without notice even in a bugfix release. Projects that > depend on it are incorrect and should be fixed. I don't think that it would hurt to document the r

[issue33666] os.errno gone AWOL

Petr Viktorin 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 i

[issue33666] os.errno gone AWOL

Serhiy Storchaka added the comment: os.errno as well as os.sys or os.abc is an implementation detail. It can be changed without notice even in a bugfix release. Projects that depend on it are incorrect and should be fixed. -- nosy: +serhiy.storchaka resolution: -> not a bug stage: -

[issue33666] os.errno gone AWOL

New submission from Miro Hrončok : In 3.7.0b4 I see the following traceback: >>> import os >>> os.errno Traceback (most recent call last): File "", line 1, in AttributeError: module 'os' has no attribute 'errno' This was not the case for Python 3.6: >>> import os >>> os.errno os.errno mig