[docs] [issue25294] Absolute imports fail in some cases where relative imports would work

Patrick Maupin report at bugs.python.org
Mon Oct 5 16:19:09 CEST 2015

Patrick Maupin added the comment:

concurrent/futures/__init__.py may be a better example than 2to3 for this issue.  It's relatively new code, it's part of the standard library, it's fairly small and self-contained, and it doesn't follow the promulgated standard.

If it's bad code, it should be modified.  If it's not bad code, then the docs shouldn't denigrate the coding style (especially not to the extent of requiring absolute imports in standard library code), because a lot of newbies take the docs to heart and spend a lot of time and energy beating up themselves and others about conformance.


Python tracker <report at bugs.python.org>

More information about the docs mailing list