[Python-bugs-list] [ python-Bugs-571343 ] Mixing framework and static Pythons

[SourceForge.net]

Bugs item #571343, was opened at 2002-06-19 23:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=571343&group_id=5470

Category: Macintosh
>Group: Python 2.2.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Jack Jansen (jackjansen)
Assigned to: Jack Jansen (jackjansen)
Summary: Mixing framework and static Pythons

Initial Comment:
We need to check that (on OS X) the error message you get when you attempt to load an extension module in the "wrong" Python (i.e. an extension module built for a static Python into a framework python or vice versa) is of a form understandable to naive users, and not of the "undefined external: foobar" variety. As the situation of having both Pythons on your system may well become commonplace this needs to be addressed in 2.2.X too.


----------------------------------------------------------------------

>Comment By: Jack Jansen (jackjansen)
Date: 2003-02-25 16:16

Message:
Logged In: YES 
user_id=45365

In Python 2.3 this doesn't seem to be a problem, you always get an error message on import if there is a problem.

In 2.2 it is a problem, which can be repeated as follows:
- Build and install a framework 2.2.X
- Add /Library/Framework/Python.framework/..../lib/python2.2 and .../lib-dynload to sys.path (at the beginning)
- run /usr/bin/python (version 2.2)
- run import test.regrtest; test.regrtest.main()
- witness weird errors culminating in a crash.

The reverse (loading non-framework modules into a framework 2.2 python)
seems to work okay.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=571343&group_id=5470