Issue 571343: Mixing framework and static Pythons (original) (raw)
Issue571343
This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.
This issue has been migrated to GitHub: https://github.com/python/cpython/issues/36771
classification
Title: | Mixing framework and static Pythons | ||
---|---|---|---|
Type: | Stage: | ||
Components: | macOS | Versions: | Python 2.2 |
process
Status: | closed | Resolution: | wont fix |
---|---|---|---|
Dependencies: | Superseder: | ||
Assigned To: | jackjansen | Nosy List: | jackjansen |
Priority: | high | Keywords: |
Created on 2002-06-19 21:49 by jackjansen, last changed 2022-04-10 16:05 by admin. This issue is now closed.
Messages (3) | ||
---|---|---|
msg11272 - (view) | Author: Jack Jansen (jackjansen) * ![]() |
Date: 2002-06-19 21:49 |
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. | ||
msg11273 - (view) | Author: Jack Jansen (jackjansen) * ![]() |
Date: 2003-02-25 15:16 |
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. | ||
msg11274 - (view) | Author: Jack Jansen (jackjansen) * ![]() |
Date: 2003-05-23 14:04 |
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. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-10 16:05:26 | admin | set | github: 36771 |
2002-06-19 21:49:23 | jackjansen | create |