[Python-Dev] PEP 250 - site-packages on Windows: (Was: [Distutils]
Package DB: strawman PEP)
Thu, 12 Jul 2001 11:14:35 +0200
"Moore, Paul" wrote:
> From: M.-A. Lemburg [mailto:email@example.com]
> Tim Peters wrote:
> > Umm, what am I missing? The change to site.py was so simple you could
> > committed it yourself quicker than it took to write the above. I
> > it a few minutes ago. If something else is needed, someone else will have
> > to do it (or explain it to me in detail so precise they could do it
> > 10x quicker <wink>).
> > Cool, but what about the changes needed in distutils to actually
> > utilize the new directory and the changes to the Windows installer
> > to create the directory at installation time ?
> The patch I sent along with the final version of the PEP included the
> distutils change (it's only one line, but it's on the PC at home, so I can't
> quote it here). I assume that the Python install should ensure that the
> site-packages exists (it does at the moment) so I don't see a need for the
> wininst installer to check.
I don't have a site-packages dir in my installations. Could it be that
you installed some distutils package which automagically created one
or that this change in Python 2.1.1 ?
> PS [After a quick rummage...] I *think* the following patch is what is
> needed for distutils: I haven't tested it, though, so it would be better to
> check the original version (which I did test...)
> --- sysconfig.py.orig Thu Apr 19 10:24:24 2001
> +++ sysconfig.py Thu Jul 12 09:32:34 2001
> @@ -87,7 +87,7 @@
> elif os.name == "nt":
> if standard_lib:
> - return os.path.join(PREFIX, "Lib")
> + return os.path.join(PREFIX, "Lib", "site-packages")
> return prefix
This doesn't seem to do the trick: the Windows installer still installs
the packages directly to \Python21.
CEO eGenix.com Software GmbH
Consulting & Company: http://www.egenix.com/
Python Software: http://www.lemburg.com/python/