[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If y

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

STINNER Victor added the comment: This issue is no newcomer friendly, I remove the "easy" keyword. -- keywords: -easy nosy: +vstinner ___ Python tracker ___ _

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

Swati Jaiswal added the comment: Can someone help with tests? I just need a pointer on how to do it. -- keywords: +patch Added file: http://bugs.python.org/file41394/iss_13317.patch ___ Python tracker _

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

Éric Araujo added the comment: I’m not active in python-dev anymore. The fix was noted in a previous comment: build.sub_commands in distutils.command.build should list "build_ext" before "build_py". lib2to3.fixes.fix_import will write global instead of local import statements else. -

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

Swati Jaiswal added the comment: are you working on it @eric? -- nosy: +curioswati ___ Python tracker ___ ___ Python-bugs-list mailing

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

Éric Araujo added the comment: For the record this is caused by #17393 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

Éric Araujo added the comment: Ah, thanks for clarifying, I didn’t understand what you meant with local/global but now I see it’s about absolute imports and explicit relative imports. (I don’t remember ever reading that terminology before looking at fix_import.) I’m adding the “easy” keyword

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

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

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

simohe added the comment: fix_imports rewrites the import statements to local or global. When a python module loads a local extension module, this import statement should be converted to a local import (from . import extensionmodule). But when the extension module is not built yet, fix_import

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

Éric Araujo added the comment: Hello and thanks for the report. > We need build_ext before build_py. Otherwise, when 2to3 is called (in > build_py), > it will not find ext modules, Why is 2to3 interested in extension modules? 2to3 converts Python code, extension modules are written in C or C

[issue13317] building with 2to3 generates wrong import paths because build_ext is run after build_py

New submission from simohe : We need build_ext before build_py. Otherwise, when 2to3 is called (in build_py), it will not find ext modules, thinking that those modules are global and, consequently, making a mess, now that all module imports are global. -- components: 2to3 (2.x to 3.x c