[Python-bugs-list] importing extensions (PR#275)

Mark Hammond mhammond@skippinet.com.au
Thu, 6 Apr 2000 09:48:26 +1000


I can not think of a good way to prevent this error.

Problem is:
* Python.exe correctly loads Python16.dll
* Python does import foo.pyd
* Loading foo.pyd forces Python15.dll to be loaded.
* Python15.dll crashes as it has not been initialized.

I can not see a good solution to this, other than a fairly heavy
solution, and even then it would only work for 1.6 vs 1.7 - ie, we
would also need some diagnostic code in the _early_ version to
handle this gracefully.

What this means is, if we want to prevent this same problem in
Python 1.7 vs Python 1.6, we need to add the code into 1.6.  It is
too late for 1.5.

Mark.



> -----Original Message-----
> From: python-bugs-list-admin@python.org
> [mailto:python-bugs-list-admin@python.org]On Behalf Of
> guido@python.org
> Sent: Thursday, 6 April 2000 4:26 AM
> To: python-bugs-list@python.org
> Cc: bugs-py@python.org
> Subject: Re: [Python-bugs-list] importing extensions (PR#275)
>
>
> > I installed python-1.6a1 (Windows) and
> > found that I couldn't import any extensions.
> > That blew wxPython as well as calldll.pyd,
> > avl.pyd and a couple I wrote myself. I should
> > have tried Numeric but I'm back to 152 now.
> > Got "abnormal program termination" on any such
> > attempt.
>
> Thanks for reporting this.  It is probably necessary that all
> extensions be recompiled for Python 1.6 (it's
> sufficiently different
> to warrant this).  But "abnormal program termination" is a
> particularly harsh response -- I'll see if we can improve the
> diagnostics somewhat!
>
> --Guido van Rossum (home page: http://www.python.org/~guido/)
>
>
>
> _______________________________________________
> Python-bugs-list maillist  -  Python-bugs-list@python.org
> http://www.python.org/mailman/listinfo/python-bugs-list
>