[issue9109] absolute import cleanups for Python 3

A.M. Kuchling added the comment: It seems to me that this issue was fixed for Python 3.3 by commit 2dd046be2c88 for #2377, which made importlib the implementation of __import__(). Python/import.c now raises a ValueError if level < 0, and the docstring has been corrected to have 'level=0' as t

[issue9109] absolute import cleanups for Python 3

Changes by Brett Cannon : -- assignee: brett.cannon -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue9109] absolute import cleanups for Python 3

Changes by Brett Cannon : -- stage: -> unit test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue9109] absolute import cleanups for Python 3

Brett Cannon added the comment: Having level=-1 doesn't even work in Python 3 like it did in Python 2 (it seems to just act as if level is 0), so yes the -1 code can be removed. Probably need all values less than 0 to get rounded up to 0 for backwards-compatibility with Python 2.x code which

[issue9109] absolute import cleanups for Python 3

Changes by Eric Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue9109] absolute import cleanups for Python 3

Changes by Neil Schemenauer : -- assignee: -> brett.cannon nosy: +brett.cannon -nas ___ Python tracker ___ ___ Python-bugs-list mailin

[issue9109] absolute import cleanups for Python 3

New submission from Neil Schemenauer : It looks like there is a bunch of legacy relative import cruft kicking around in Python 3. The first thing I noticed is that __import__.__doc__ claims that level=-1 is the default (i.e. use the Python 2 behavior). A little testing shows that the docs do