Jari Pennanen added the comment:
> Note that I don't think that just providing an alternative order of
build_py and build_ext would solve the SWIG issue - e.g. build_py
wouldn't know about the new files SWIG generates unless the SWIG build
process explicitly tells the build_py
New submission from Jari Pennanen :
Long story short: Sometimes build_ext should be run before build_py, or
something similar.
As an example when using SWIG and setup.py the build order is incorrect:
During build_ext the SWIG generates .py files that should be used during
build_py, but since
