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 ins
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
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 i
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
