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 jlvandenhout
Recipients dstufft, eric.araujo, jdemeyer, jlvandenhout
Date 2019-06-12.21:09:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560373759.98.0.479227614943.issue37247@roundup.psfhosted.org>
In-reply-to
Content
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 <package>', the build sequence is predefined anyways, unless you explicitly define your own sequence in a custom command, in which case you are already tempering with default behavior.

That's why I argue that building and copying SWIG generated files correctly should be the default behavior.
History
Date User Action Args
2019-06-12 21:09:20jlvandenhoutsetrecipients: + jlvandenhout, eric.araujo, jdemeyer, dstufft
2019-06-12 21:09:19jlvandenhoutsetmessageid: <1560373759.98.0.479227614943.issue37247@roundup.psfhosted.org>
2019-06-12 21:09:19jlvandenhoutlinkissue37247 messages
2019-06-12 21:09:19jlvandenhoutcreate