>> I thought the original proposal was to install a *binary* easy_install >> that takes that function. > > What do you mean by "binary"? I thought we were talking about a > module. Do you mean a script to be installed alongside Python itself in > e.g. /usr/bin?
Exactly so. > In the original discussion, it was a module to be added alongside > pkg_resources, which would use pkg_resources to find and/or install > setuptools. I also personally like the use of -m instead of a script > because it makes it quite clear that this is a Python-specific > installation tool, and *which* version of Python, as well, without > having to have easy_install-2.5, easy_install-2.6, etc. If that becomes the official interface to easy_install, that's fine with me. I'm worried about web instructions that tell people that there is an "easy_install" utility, so that people never find out the module actually exists. Regards, Martin _______________________________________________ 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
