I still think that Python needs to fix the problem with the API between the core and the extensions. That way all the version checking would work for Windows and Unix. But since that approach has been rejected I'd take any change to python that reduces support calls. BArry
-----Original Message----- From: python-dev-admin@python.org [mailto:python-dev-admin@python.org]On Behalf Of Mark Hammond Sent: 29 September 2000 02:36 To: python-dev@python.org Subject: [Python-Dev] Patch to avoid conflict with older versions of Python.
Hi all, I'd like some feedback on a patch assigned to me. It is designed to prevent Python extensions built for an earlier version of Python from crashing the new version.
I haven't actually tested the patch, but I am sure it works as advertised (who is db31 anyway?).
My question relates more to the "style" - the patch locates the new .pyd's address in memory, and parses through the MS PE/COFF format, locating the import table. If then scans the import table looking for Pythonxx.dll, and compares any found entries with the current version.
Quite clever - a definite plus is that is should work for all old and future versions (of Python - dunno about Windows ;-) - but do we want this sort of code in Python? Is this sort of hack, however clever, going to some back and bite us?
Second related question: if people like it, is this feature something we can squeeze in for 2.0?
If there are no objections to any of this, I am happy to test it and check it in - but am not confident of doing so without some feedback.
Thanks,
Mark.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://www.python.org/mailman/listinfo/python-dev