[issue15482] __import__() change between 3.2 and 3.3

Changes by Brett Cannon : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue15482] __import__() change between 3.2 and 3.3

Roundup Robot added the comment: New changeset 3fe01f7520e2 by Brett Cannon in branch '3.2': Issue #15482: Properly document the default 'level' parameter for http://hg.python.org/cpython/rev/3fe01f7520e2 New changeset 05bec2e78a5c by Brett Cannon in branch 'default': Issue #15482: Merge 78449:3

[issue15482] __import__() change between 3.2 and 3.3

Brett Cannon added the comment: I just realized my reply was unclear; I meant changing Doc/library/functions.rst, not the code. And 3.3 already has a versionchanged note about no longer accepting negative indexes, but I will update it to mention the new default as well explicitly. --

[issue15482] __import__() change between 3.2 and 3.3

Brett Cannon added the comment: On Jul 29, 2012 5:58 AM, "Martin v. Löwis" wrote: > > > Martin v. Löwis added the comment: > > So should 3.2 be changed to adjust the default value to match the documentation? It is probably safe to do so. -brett > > -- > nosy: +loewis > > _

[issue15482] __import__() change between 3.2 and 3.3

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15482] __import__() change between 3.2 and 3.3

Martin v. Löwis added the comment: So should 3.2 be changed to adjust the default value to match the documentation? -- nosy: +loewis ___ Python tracker ___ __

[issue15482] __import__() change between 3.2 and 3.3

Nick Coghlan added the comment: s/not added/note added/ -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue15482] __import__() change between 3.2 and 3.3

Nick Coghlan added the comment: The specific bug is that, in 3.2, the claimed default (level=0) is not accurate: the default is actually (level=-1), as it was in 2.x. The import statement passes level=0 explicitly (as it does in 2.x when "from __future__ import absolute_import" is in effect).

[issue15482] __import__() change between 3.2 and 3.3

Eric Snow added the comment: See issue14592 (particularly msg158466). -- nosy: +eric.snow ___ Python tracker ___ ___ Python-bugs-list

[issue15482] __import__() change between 3.2 and 3.3

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__('ba