[issue7902] relative import broken

Florent Xicluna added the comment: Merged in 3.1 with r84115. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7902] relative import broken

Barry A. Warsaw added the comment: Guido has spoken: http://mail.python.org/pipermail/python-dev/2010-August/103104.html We'll keep the change for 2.6.6rc2. -- nosy: +barry status: open -> closed ___ Python tracker

[issue7902] relative import broken

Florent Xicluna added the comment: Comment changed in r84097, 3.2 branch, with minor fixes. -- ___ Python tracker ___ ___ Python-bugs-

[issue7902] relative import broken

Florent Xicluna added the comment: Btw, the comment and failure message in r81380/r81381 look wrong. -# If absolute import syntax is used, then do not try to perform -# a relative import in the face of failure. +# If explicit relative import syntax is used, then do not try +# to

[issue7902] relative import broken

Changes by Martin v. Löwis : -- priority: normal -> release blocker status: closed -> open ___ Python tracker ___ ___ Python-bugs-list

[issue7902] relative import broken

Martin v. Löwis added the comment: Backporting this change to 2.6 has created an incompatibility in that branch, see for example issue9600. Apparently, it will only break code that is "conceptually wrong", but still "worked" on 2.6. I'll suggest that this is a release-critical issue for 2.6.6

[issue7902] relative import broken

Brett Cannon added the comment: Thanks for the patch, Meador. All I did was tweak the test slightly. Committed in: + 2.7: r81380 + 2.6: r81381 -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python trac

[issue7902] relative import broken

Changes by Brett Cannon : -- assignee: -> brett.cannon keywords: +needs review stage: -> patch review ___ Python tracker ___ ___ Pyth

[issue7902] relative import broken

Meador Inge added the comment: Does this patch seem reasonable? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue7902] relative import broken

Meador Inge added the comment: > So doing the import manually through __import__('os', globals(), > locals(), ['walk'], 1) does not work. I get the same behavior for this reproduction case regardless of whether I use: import .os import walk or: __import__('os', globals(), locals(), ['wa

[issue7902] relative import broken

Changes by Oren Held : -- nosy: +Oren_Held ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue7902] relative import broken

Brett Cannon added the comment: So doing the import manually through __import__('os', globals(), locals(), ['walk'], 1) does not work. My guess is it has something to do with the IMPORT_FROM opcode (or something related), but I don't have time right now to dig deeper. -- ___

[issue7902] relative import broken

ganges master added the comment: i believe brett is in charge of this, adding him to the noisy. sorry if it's not you :) -- nosy: +brett.cannon ___ Python tracker ___ __

[issue7902] relative import broken

New submission from ganges master : the relative-import mechanism is broken... at least on python2.6 but i'd guess on later versions as well. consider this package layout: /tmp/foo/ /tmp/foo/__init__.py /tmp/foo/bar.py where bar.py is: # note this is a relative import and shoul