[issue8358] absolute_import future directive ignored by 2to3

Benjamin Peterson added the comment: Fixed in r79917. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Pytho

[issue8358] absolute_import future directive ignored by 2to3

Changes by R. David Murray : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue8358] absolute_import future directive ignored by 2to3

Jason R. Coombs added the comment: I found a workaround by excluding the "import" fixer that seems to work. For the example, > 2to3 -x import abs_imp_test The command still modifies main, but it only removes the __future__ directive and doesn't modify the imports. For my real-world package,

[issue8358] absolute_import future directive ignored by 2to3

Jason R. Coombs added the comment: More importantly, is there a workaround for main.py that will work in Python 2, and in Python 3 after 2to3, that doesn't require any module renaming? -- ___ Python tracker __

[issue8358] absolute_import future directive ignored by 2to3

New submission from Jason R. Coombs : I'm using Python 3.1.2 64-bit on Windows. I've found that even if "absolute_import" is imported from __future__, 2to3 will convert imports to be treated as relative. To demonstrate this behavior, I created a small package "abs_imp_test" (attached). abs_i