This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients ciantic, lemburg, tarek
Date 2009-12-22.21:18:33
SpamBayes Score 1.20994e-08
Marked as misclassified No
Message-id <>
The distutils way of implementing a different fixed order would be to
create a build command sub-class, override the .sub_commands list and
then register this new subclass as 'build' command with distutils via
the cmdclass setup() keyword argument. (eGenix uses this approach in - see egenix-mx-base)

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 command about these new files.

It would probably be better to add a completely new command just for
managing the SWIG build process to distutils. This could then add the
generated files, run build_ext with the required special arguments,
rerun build_py, etc.
Date User Action Args
2009-12-22 21:18:37lemburgsetrecipients: + lemburg, tarek, ciantic
2009-12-22 21:18:37lemburgsetmessageid: <>
2009-12-22 21:18:34lemburglinkissue7562 messages
2009-12-22 21:18:33lemburgcreate