[ python-Bugs-1069198 ] OS X (Panther) Framework Install causes
version mismatch
SourceForge.net
noreply at sourceforge.net
Wed Nov 24 21:22:11 CET 2004
Bugs item #1069198, was opened at 2004-11-18 22:38
Message generated for change (Comment added) made by maparent
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1069198&group_id=5470
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Dusty Harr (daveron)
Assigned to: Nobody/Anonymous (nobody)
Summary: OS X (Panther) Framework Install causes version mismatch
Initial Comment:
Installed from source python version 2.3.4 (framework install) I
am running panther (10.3.6)
Following directions in readme
./configure --enable-framework
make
sudo make frameworkinstall (this last step fails without root privs,
maybe docs should include the sudo??)
after this python will give the following error:
Interpreter not initialized (version mismatch?)
I tracked this down to python installing into
/Library/Frameworks/Python.Framework
when the apple-python is installed into
/System/Library/Frameworks/Python.Framework
Aparently it was loading the older librarys from the
/System/Library folder since it comes before the /Library folder in
the search path.
to the casual observer however everything seams fine and dandy
at first because the python binaries are put into /usr/local/bin
which is also later down the search path than the apple supplied
ones in /usr/bin ! it is not untill you use the new binaries by
specifying the full path that you find out they don't even work :)
Deleting /System/Library/Frameworks/Python.Framework resolved
the issue for me. (i deleted the apple supplied binaries from /usr/
bin as well so these files where un-needed)
----------------------------------------------------------------------
Comment By: Marc-Antoine Parent (maparent)
Date: 2004-11-24 15:22
Message:
Logged In: YES
user_id=153018
I agree it could be made more explicit, but a good solution is to ensure
the Python framework install replaces the one in the system, which can
be obtained with the following configure flag:
--enable-framework=/System/Library/Frameworks
----------------------------------------------------------------------
Comment By: Bob Ippolito (etrepum)
Date: 2004-11-24 04:05
Message:
Logged In: YES
user_id=139309
This is a configuration problem on your computer, not a general problem
with installing Python 2.3.4 on a Mac OS X 10.3 system.
This error happens primarily if two Python libraries are linked into the
same executable. This can happen if you load an extension compiled
with the system Python from your custom Python or vice versa. On Mac
OS X 10.3, this doesn't have to be the case, as there are linker flags that
can avoid this situation. Python 2.3.4 uses these linker flags (at least if
you have the MACOSX_DEPLOYMENT_TARGET environment variable set to
"10.3" when you configure). Python 2.3.0, as shipped by Apple in OS X
10.3, did not use these flags, so it has this problem. In this situation,
Python 2.3.0 can use extensions built with Python 2.3.4, but not vice
versa.
By default /usr/local/bin isn't in the search path at all, IIRC. If you
wanted your Python to come first in the path, you should've changed
your PATH, instead of removing essential system files. Your
configuration is now even more broken, and several applications will no
longer work correctly.
Anyway, this is not really a bug (in Python 2.3.4) at all.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1069198&group_id=5470
More information about the Python-bugs-list
mailing list