On Mon, Nov 9, 2015 at 3:27 AM, James Bennett <ubernost...@gmail.com> wrote:
> Python scripts directly and without having to do hackery with > supporting/requiring 'python -m' or similar is too useful and commonly > used. So faced with either (essentially) forcing a trend of every > command-line tool having to be invoked with 'python -m', > pip is a special case -- for MOST python command line tools, the user does not care which python it is running with -- if it works, it works. the failure case we are trying to address here is when "pip install" works sjtu fine -- it finds and installs the package into the python pip is associated with -- it just doesn't do what the user wants and expects! any other script can be run with any python that will work -- if a user has ten different versions of python installed, and every different python-bsed tool they use uses a different one -- who cares, as long as it works. or requiring people with complex multi-Python installations to be more > careful, I choose the "be more careful" option (i.e., I would strenuously > resist changing Django's admin script to "python -m django" if this were > proposed to Django today). > Well, the exception to the above is people developing those scripts, but they should know better -- and so should a sysadmin instaling a django app. -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig