> First, Skip, I *only* care about the default behavior. There's already > a way to do it differently: PYTHONPATH. So, Fred, I think what you're > arguing for is to drop this feature entirely. Or is there some other > use for a new way to allow users to explicitly add something to > sys.path, aside from PYTHONPATH? It seems that it would add more > complexity and I can't see what the value would be.
PYTHONPATH is lacking one feature which is important for lots of packages and setuptools. The directories in PYTHONPATH are just added to sys.path. But setuptools require a site package directory. Maybe a new env var PYTHONSITEPATH could solve the problem. > As I've said a dozen times in this thread already, the feature I'd like > to get from a per-user installation location is that 'setup.py install', > or at least some completely canonical distutils incantation, should > work, by default, for non-root users; ideally non-administrators on > windows as well as non-root users on unixish platforms. The implementation of my PEP provides a new option for install: $ python setup.py install --user Is it sufficient for you? Christian _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
