[issue12864] 2to3 creates illegal code on import a.b inside a package

Change by Irit Katriel : -- resolution: duplicate -> wont fix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12864] 2to3 creates illegal code on import a.b inside a package

Change by Irit Katriel : -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed superseder: -> Close 2to3 issues and list them here ___ Python tracker

[issue12864] 2to3 creates illegal code on import a.b inside a package

Changes by Meador Inge : -- nosy: +meador.inge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue12864] 2to3 creates illegal code on import a.b inside a package

Éric Araujo added the comment: BTW I think if this is too difficult to implement 2to3 could just be documented as requiring you not to use implicit relative imports. -- ___ Python tracker

[issue12864] 2to3 creates illegal code on import a.b inside a package

Éric Araujo added the comment: -import sub.subsub +from .sub import subsub as _dummy That’s partly incorrect, as you need to bind the name sub to match the original code. -- nosy: +eric.araujo ___ Python tracker

[issue12864] 2to3 creates illegal code on import a.b inside a package

Changes by Éric Araujo : -- nosy: +benjamin.peterson stage: -> needs patch versions: +Python 2.7, Python 3.2, Python 3.3 -Python 2.6, Python 3.1 ___ Python tracker ___ _

[issue12864] 2to3 creates illegal code on import a.b inside a package

New submission from simohe : When the current module is in a package and imports submodules, the following lines are converted to illegal code. -import sub.subsub +from . import sub.subsub -import sub, sub.subsub, sub2 +from . import sub, sub.subsub, sub2 A valid alternative: -import sub.sub