➜

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.23:19:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560381559.51.0.291235565337.issue37247@roundup.psfhosted.org>
In-reply-to
Content 
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 copied first or not. In the non-SWIG case they are truly independent commands. It is only in the SWIG packages that they become dependent on each other.

On top of that I see more and more questions on stack exchange and other forums asking why their SWIG builds fail to install correctly, implying that more and more developers are using this awesome feature and start to rely on it.
History
Date User Action Args
2019-06-12 23:19:19jlvandenhoutsetrecipients: + jlvandenhout, eric.araujo, jdemeyer, dstufft
2019-06-12 23:19:19jlvandenhoutsetmessageid: <1560381559.51.0.291235565337.issue37247@roundup.psfhosted.org>
2019-06-12 23:19:19jlvandenhoutlinkissue37247 messages
2019-06-12 23:19:19jlvandenhoutcreate