Author ned.deily
Recipients Alex.Burka, Julian, benjamin.peterson, ezio.melotti, georg.brandl, mrabarnett, ned.deily, samueljohn, serhiy.storchaka
Date 2013-05-28.21:44:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369777488.23.0.0591679326375.issue18050@psf.upfronthosting.co.za>
In-reply-to
Content
Serhly, while I don't disagree with your points, I should have made clearer that the issue here is that the _sre module is a static module (built into the interpreter executable or shared lib as shown in Modules/Setup.dist) and *not* included in the shared library (sys.prefix/lib/pythonX.Y/) whereas are_constants *is*. If the binaries produced by both the python and C files changes end up in sys.prefix/lib/pythonX.Y, there is not a problem.  That's normally the case and I believe that is the case with both of the other examples you cited.  So they are not going to exhibit this problem.  The problem is when a change introduces a dependency between static and shared modules, like this one does.
History
Date User Action Args
2013-05-28 21:44:48ned.deilysetrecipients: + ned.deily, georg.brandl, benjamin.peterson, ezio.melotti, mrabarnett, samueljohn, Julian, serhiy.storchaka, Alex.Burka
2013-05-28 21:44:48ned.deilysetmessageid: <1369777488.23.0.0591679326375.issue18050@psf.upfronthosting.co.za>
2013-05-28 21:44:48ned.deilylinkissue18050 messages
2013-05-28 21:44:48ned.deilycreate