On 12 October 2010 00:42, Giampaolo Rodolà <g.rodola at gmail.com> wrote: > I know. My point was you can't do it by default and installing a > module is something even a less experienced user usually does. > Typing "C:\PythonXX\pysetup" is harder compared to "setup.py install" > and solving this problem by modifying your environment paths so that > you can just type "pysetup" is something I would expect to be done by > the MSI installer, not the user. I would assume (am I wrong?) that the canonical way of installing modules on Windows for "non-advanced" users under distutils2 would still be to download and run a binary installer. Assuming that's the case, modifying paths to make sure pysetup is available as a command is no harder than making Python itself available. (Having said that, I'd still personally prefer to have the distutils2 command be invoked by some form of python -m invocation). Paul.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4