On 10/21/2010 07:13 PM, Greg Ewing wrote:
Eric Smith wrote:
Or for that matter a plain "pysetup". It would be the one that a plain
"python" would get you.
If 'pysetup' is simply a shell script that invokes 'python -m setup'
using the current search path, I guess that's true.
On Windows, however, it seems to me that the current 'python setup.py'
scheme has advantages, since it lets you simply invoke 'setup.py' and
rely on file associations to get you the current python. Supporting
either 'python -m setup' or 'pysetup' out of the box would require
install-time path hacking of the sort that some people are uncomfortable
about.
Terek said this in the first post of this thread...
I just wanted to make sure that once distutils2 is back in the stdlib,
it's OK for us to add that script in the distribution.
When it's in the stdlib, the -m option should work just like any other
script run from the stdlib.
What path hacking are you thinking of?
Ron
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
