Bill Janssen wrote:
Michael McCandless <luc...@mikemccandless.com> wrote:
Michael McCandless wrote:
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 ;)
Though...
It'd be much better if installs from python.org could cleanly co-
exist
with
Apple's default installs.
Is there some suggestion/patch we could make to python.org to do
that?
Well, we yak about it every now and then on the Mac-SIG Python list.
And it more or less does, as long as you keep /usr/local/bin off your
PATH. But there are all these meta-issues about people's paths, and
Ahh.... so I *did* have /usr/local/bin on my path.
Apple not releasing Python updates, etc. IMO, this is really caused
by
developer-consumer culture clash. Apple builds for consumers, who
will
always just use the Python they got with the machine, and expects
developers to know what they're doing. (Linux, on the other hand,
builds for developers, and expects consumers to know what they're
doing :-).
:) Makes sense I guess. I just don't know what I'm doing ;)
A few more rules I find useful on the Mac:
* never trust anything in /usr/local/bin to work
* never use fink -- build from source
* never use macports -- build from source
* never set LD_LIBRARY_PATH or DYLD_LIBRARY_PATH
(good advice on Linux, too)
* never trust a package which requires you to break one of the
above rules
These are excellent.
Isn't this off-topic?
Yeah, sure is... I'll stop asking questions!
Mike
