Excuse my ignorance, but isn't the whole problem that the python 1.6 DLL is in the system search path even when you are running Python 1.7? MacPython solves this problem by keeping the PythonCore dll in the application directory, so it'll be found by a Python executable in the same directory but not by a python executable living elsewhere. And even if you import a dynamic module that was meant for and older or newer version of Python you'll get a decent error message: because all PythonCore's have the same name the imported module will link against the one already loaded and complain bitterly about missing externals (all assuming the current PythonCore and the module aren't compatible). This is a bit of a simplification, because MacOS doesn't really use the dll filename for matching the library, and there are extreme cases where you can end up with two PythonCore's in one process (but they don't happen to the average user), but this is the general idea.... -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4