[Python-Dev] Preventing 1.5 extensions crashing under 1.6/2.0 Python

Barry Scott barry@scottb.demon.co.uk
Mon, 10 Jul 2000 21:09:20 +0100

> There are endless variations on this theme.  What's missing at the
> moment is a bit of requirements analysis.  What's the problem we're
> trying to solve here?  So far, the only problem that came up was that
> on Windows, you get an obscure crash when trying to load an extension
> built for Python 1.5(.x).  Do we really need a whole new version
> negotiating architecture?  You can already get the version string by
> looking at Py_GetVersion() -- this also answers the question of how a
> version is represented.

I post the first mail as I think it reflects poorly on Python if it
crashes for this preventable reason.

How important this problem is depends on how many users it will
affect. Is it only a few .pyd that fail or all of them? Will a few
users see this or lots of them?

I'd hope one requirement is not to look bad in the eyes of the
python users.

When the old extension calls Py_GetVersion() it will be the
python15.dll:Py_GetVersion(). Not the new one.

Integer version values would be nicer to handle then hacking
a string up.