Ned Deily added the comment: 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.
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18050> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
