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.

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.

Logged In: YES 
user_id=45365

It turns out 2.2.3 gives the correct error message "(Fatal Python error: 
Interpreter not initialized (version mismatch?)" when importing a 2.3 
framework-Python module.

Theoretically it may give the wrong error message when importing a 2.2.3 
framework-Python module, but I don't think many people will build 2.2.3 
framework builds, as they have little extra to offer over the non-framework 
builds.