On Jan 28, 2008, at 10:25 PM, Jon Crump wrote:
Ah, thanks very much for the explanation. It seems to me that the
best thing to do is to move my site-packages directory into the /
System/Library/Frameworks branch and then delete the Python
installation in the /Library/Frameworks branch.
Ack! Please don't do that. Everything in /System/ is supplied by
Apple and should be left alone. However, if you look, I think you'll
find that the site-packages/ directory in /System/Library/Frameworks/
Python.framework/ is a symlink to someplace in /Library/ (I don't
have Leopard, so I don't know for sure, but on my Tiger install /
System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/
site-packages points to /Library/Python/2.3/site-packages). site-
packages/ is thus a safe place for you to put things, and Python
should do so automatically when you run setup.py (but you have to be
sure to run the proper variant of python (see below)).
You have two options:
1) keep your secondary installation of Python in /Library/ and modify
your path according to QA1067, as Jim provided. There's nothing
inherently wrong with this. Apple is rather conservative about
updating things like Python, so you might well find a time in the
future where you'll want a newer one than they provide, but you
should *not* mess directly with what they supply. Many aspects of the
system may be expecting to find a particular version of Python. I
think you'll find that /usr/bin/python will invoke the version in /
System/ and /usr/local/bin/python will invoke the version in /
Library/. This way you can have both present and actively use the one
you want.
2) Move the contents of your /Library/ site-packages/ into wherever /
System/'s points. Then you can get rid of your installation in /
Library/.
What modifications should I then make to $PATH? Is it enough simply
to remove the contents of /Library/Frameworks/Python.framework/ ?
When I install packages in future, will setup.py know where to
install things?
Yes, it should.
the Headers directory turns out to be full of xxx.h files, do I
need these? CodeResources turns out to be a .plist, I presume I
need that? I know these questions betray profound ignorance but I'd
be grateful if you bear with me. I feel I must harmonize these two
separate python installations or else it will come around to bite
me in the future I'm sure.
You need everything in /System/Library/Frameworks/Python.framework/.
Leave it alone.
If you choose to continue using /Library/Frameworks/
Python.framework/, then you should leave it alone, too. Many packages
consist only of Python code, but some will be profoundly unhappy if
they can't find the proper headers to compile against. If you choose
*not* to continue using /Library/Frameworks/Python.framework/, then
just delete the whole thing; there's no reason to pick through it,
other than your site-packages.
--
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <[EMAIL PROTECTED]>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
