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 cstratak
Recipients cstratak, gregory.p.smith, ned.deily, octavian.soldea, vstinner
Date 2018-12-07.20:39:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hi Ned,

I recently pushed a fix on the master and 3.7 for this exact issue: but it builds on top of which is not yet in 3.6.

Thus 3.7 is fine for the rc cutoff.

However there is another side effect of that change with the linker flags also leaking: but it proved to be more complicated than what I initially thought to fix it.

PR here:

The issue is that I figured it wouldn't make it to the 3.6 branch as it would require extensive review due to the complexity of the build system and the requirement for extensive review to catch any possible regressions, thus it would be late for the rc cutoff.

It would take some days to figure out everything I believe. Would it be possible to push that after rc1? Or maybe not fixing that would be better, deadline wise? I consider this an important issue but some more feedback is always welcome.

Side note on your comment: The compiler used (CC) also seems to leak into distutils instead of the system default CC, on linux with 'python3 build'.
Date User Action Args
2018-12-07 20:39:04cstrataksetrecipients: + cstratak, gregory.p.smith, vstinner, ned.deily, octavian.soldea
2018-12-07 20:39:04cstrataksetmessageid: <>
2018-12-07 20:39:04cstrataklinkissue31354 messages
2018-12-07 20:39:04cstratakcreate