Charles Hartman wrote:
> I think that part of what confuses a non-Unix person like me is the
> distinction PATH / (executable programs and scripts) vs. PYTHONPATH /
> modules. (This comes up with IPython because embedding its interpreter
> in another program requires importing a module IPShellEmbed.)
Usually, they really are totally unrelated, but I guess it can be
confusing when a package contains a program and also modules for use
with other programs.
> I find
> that my environment contains no PYTHONPATH variable, presumably because
> I've just been using the modules supplied with Python and with wxPython,
> and the installers have put them in (some) default places. So I assume
> that the new installer, too, won't set a PYTHONPATH.
I have never needed a PYTHONPATH. Almost everything gets installed to
the default location (site-packages). That's probably the case for
almost all people that are the primary user of their machine.
The main exception is if you have a bunch of modules you want to use
that you don't want to install in the system python. I've never had a
need for that, but some do.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
[EMAIL PROTECTED]
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
