Fri Jan 19 08:13:01 2001
Thomas Heller wrote:
> From: "Moore, Paul" <Paul.Moore@uk.origin-it.com>
> > >
> > > distutils on windows always installs to this directory. bdist or
> > > otherwise. i don't see any need for change?
> > I asked this once before. I gather that it's a Guido-mandated standard. I
> > dislike it intensely, however. I think that user-installed modules should be
> > segregated from standard ones. The obvious place is
> > <PythonDir>\Lib\site-packages. But that needs site.py to change to handle
> > this directory on Windows, as well as on Unix (I see no logic to why it
> > doesn't already). At the very least, <PythonDir>\Local would be better, with
> > distutils creating the directory, and probably adding a Local.pth, if it
> > doesn't already exist.
> > I hate this default so much that I *always* download sources, and do python
> > setup.py build, and then install by hand. This is stupid.
> > At the absolute minimum, the install target should allow specifying an
> > alternative target. And the wininst installer needs to offer the user a
> > choice of install directory.
> wininst once had such an option. I removed it because of Greg's suggestion:
> The developer can override it by using the 'extra_path'
> option to the setup function.
I guess it would be possible to put this option into setup.cfg,
but we'll still need some standard... otherwise all packages
will end up using their own little twist.
There's one catch though: extra_path would only be necessary for
Windows installations and not for Unix ones.
Python Pages: http://www.lemburg.com/python/