[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

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

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

John Andersen added the comment: I haven't made much progress on the fix yet. But I have a workaround here: https://github.com/tpm2-software/tpm2-pytss/commit/9952e374b4d9b854aea12c667dd7d7ab4ad501a9 -- ___ Python tracker

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

John Andersen added the comment: I'm going to take a stab at this by adding build_swig which will run if the list of files only contains .i files. -- ___ Python tracker ___

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

Change by John Andersen : -- nosy: +pdxjohnny ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

Jeroen van den Hout added the comment: > Adding a separate build step for SWIG (then the order would be build_swig, > build_py, build_ext) would be safer and IMHO also more logical. I like this suggestion and contemplated it. However SWIG interface files are defined in Extension instances,

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

Jeroen Demeyer added the comment: > I would argue the sequence doesn't really matter that much for non SWIG > packages I don't think that this is correct. Or at least, it's not obvious to me that this is correct. It's not uncommon for projects to extend distutils in various ways and the

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

Jeroen van den Hout added the comment: I'm sorry, I read your comment completely wrong, so please disregard my previous comment. I would argue the sequence doesn't really matter that much for non SWIG packages, since those will install correctly no matter if the extensions are built and

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

Jeroen van den Hout added the comment: Well, if I look at the source code build_ext explicitly calls for SWIG to handle interface files. Also, in case of commands like 'pip install ', the build sequence is predefined anyways, unless you explicitly define your own sequence in a custom

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

Jeroen Demeyer added the comment: > SWIG creates the files correctly in the build_ext command One could argue that running SWIG should be an entirely different step, not part of build_ext. I'm afraid that your idea of swapping build_ext and build_py will be rejected because it has a high

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

Change by Roundup Robot : -- keywords: +patch pull_requests: +13878 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14014 ___ Python tracker ___

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

New submission from Jeroen van den Hout : Currently when building an extension which lists a SWIG interface (.i) file as a source file, SWIG creates the files correctly in the build_ext command. Unfortunately this command is run after the build_py command, so the python files (.py) created