Phillip J. Eby wrote: >>I think we need a simple way to handle custom directories that is: >> >>- cross platform >> >>- doesn't require modifying the Python install >> >>- allows chained/multile custom directories, which means the trick >> of putting eggs and scripts in the same directory doesn't work, > > > PYTHONPATH-based installs allow all of this, as long as you add the > setuptools .egg to PYTHONPATH.
Would putting sys.path manipulations directly into the generated scripts handle all these issues, then? Including the Windows problem of environmental variables being hard to access. >>It appears that this has something to do with your plugin proposal. > > > Not that I'm aware of, actually. The plugin facility is intended for an > "application instance" path, distinct from a general/global installation > location. Aren't we talking about setting up application instance paths here, except where the application is Python itself? -- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
