Bill Janssen wrote:
Michael McCandless <luc...@mikemccandless.com> wrote:
Bill Janssen wrote:
Michael McCandless <luc...@mikemccandless.com> wrote:
But why do I have two separate 2.5 Python installs, compiled w/
different options, in the first place? It's weird and I'd like to
fix
it, I think (outside of building PyLucene, for my own sanity).
One (the one in /Library) is the Python.org install, which I avoid
religously on the Mac, for exactly these reasons. You should be
able
to delete it without problems, and also delete the Python
executables
and similar stuff in /usr/local/bin/.
I say you *should* be able to, but I'm always leery of this. Try
just
removing all the read and execute privileges first, and see how
things
go. Then you can actually delete it when/if you need space.
Ahhhh OK; this is quite confusing.
Everyone seems to find it so. I advise Mac users at PARC to just use
the system Python (unless and until they really know what they are
doing).
I will now do the same to all Mac+Python people I know & meet ;)
This is further complicated by the fact that OS X also uses
/Library/Python/2.5/site-packages/ as the place for users to install
additional Python modules; this, for instance, is where your "lucene"
and "JCC" modules will wind up. So it's not *all* of "/Library", just
"/Library/Frameworks/Python.framework/", that you want to avoid.
Yeah, I had also noticed this confusing yet-another-difference...
I just renamed my /Library/Framework/Python.framework{,.old} and that
did
the trick.
Mike
