Ronald Oussoren <ronaldousso...@mac.com> added the comment: But should PYTHON_API_VERSION be increased for the 2.7 release?
I think it should because of the binary incompatible differences between 2.5 and 2.6. In a perfect world that would have resulted in an increase of PYTHON_API_VERSION for the 2.6.0 release, but that's something that slipped through the cracks. By increasing the value in 2.7.0 users that switch from 2.5 to 2.7 get warnings that should help then find why their compiled extension stopped working (users migrating from 2.6 to 2.7 would also get the warning while it is technically not necessary, but that's harmless because you shouldn't reuse extensions anyway). The primary reason for posting this issue was that a colleague ran into this problem: he compiled an extension on a machine with python2.5 and ran the result on a machine with python2.6 and that misteriously didn't work (in his defense: he thought that both machines ran the same version of python). A warning at import would have made it more clear what was going wrong. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8118> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
