On Oct 12, 2010, at 12:24 PM, Greg Ewing wrote: >Giampaolo Rodolà wrote: > >> If that's the case what would I type in the command prompt in order to >> install a module? >> "C:\PythonXX\pysetup.exe"? >> If so I would strongly miss old "setup.py install". > >Another thing bothers me about this. With the current scheme, >if you have multiple Pythons available, it's easy to be sure >that you're installing into the right one, because it's the >one that you use to run setup.py. Whereas if installation is >performed by a different executable, there's a possibility >of them being out of sync. > >So I think I'd prefer some scheme involving 'python -m ...' >or some other option to Python itself, rather than a separate >executable. This is why I suggested that 'setup.sh' (or whatever) take a --python-version option to select the python executable to use. Whatever solution is implemented definitely needs to take the multiple-installed pythons into account. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20101012/d5d3d299/attachment.pgp>
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