New submission from Ronan Lamy: I noticed a change in the behaviour of __import__() between 3.2 and 3.3. It looks like in 3.2 __import__() does a Py2-style combo relative/absolute import. Here's a minimal test case:
$ ls foo bar.py __init__.py __pycache__ $ cat foo/__init__.py __import__('bar', globals(), locals()) $ python3.3 -c "import foo" Traceback (most recent call last): File "<string>", line 1, in <module> File "./foo/__init__.py", line 1, in <module> __import__('bar', globals(), locals()) ImportError: No module named 'bar' $ python3.2 -c "import foo" $ I believe that 3.3 is correct and that 3.2 is wrong but can't be changed now, so I suppose that 3.2 should just document the actual behaviour of __import__() and 3.3 should document the change. (The context is that I encountered issue 15434. This looks related, but I'm not sure it is.) ---------- assignee: docs@python components: Documentation, Interpreter Core messages: 166706 nosy: Ronan.Lamy, brett.cannon, docs@python, ncoghlan priority: normal severity: normal status: open title: __import__() change between 3.2 and 3.3 versions: Python 3.2, Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15482> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com