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 erik.bray
Recipients Alexander.Sulfrian, Dan Mick, Joshua.J.Cogliati, Xuefer.x, dstufft, eric.araujo, erik.bray, jrincayc, ned.deily, ronaldoussoren, tarek
Date 2016-04-18.13:07:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1460984880.34.0.852469109196.issue8027@psf.upfronthosting.co.za>
In-reply-to
Content
I'm also inclined to agree that the buggy code (and it *is* buggy even if it was meant to fix something originally) should be removed outright.  Nobody can point to a real world issue that it fixes anymore, yet we can point to real world consequences caused by this bug still.

However, I could also agree that this should come with better support for CXXFLAGS and CXXLINK.  It's no wonder these variables are ignored by CPython--it doesn't use any c++.  That said, extension module compilation is tied, through distutils, to CPython. And there are plenty of c++ extension modules in the wild that are affected.  So it's worth addressing how these variables are used--or rather not used properly--by distutils.

I'd be happy to take a look at that if that sounds like a good approach?  Otherwise I'd push for accepting some versions of the existing patches by Joshua.J.Cogliati that remove the buggy code.
History
Date User Action Args
2016-04-18 13:08:00erik.braysetrecipients: + erik.bray, ronaldoussoren, tarek, ned.deily, eric.araujo, jrincayc, Xuefer.x, Alexander.Sulfrian, dstufft, Joshua.J.Cogliati, Dan Mick
2016-04-18 13:08:00erik.braysetmessageid: <1460984880.34.0.852469109196.issue8027@psf.upfronthosting.co.za>
2016-04-18 13:08:00erik.braylinkissue8027 messages
2016-04-18 13:07:59erik.braycreate