Message140596
| Author |
eric.araujo |
| Recipients |
ajaksu2, docs@python, eric.araujo, lambacck, python-dev, tautology, terry.reedy |
| Date |
2011年07月18日.15:39:21 |
| SpamBayes Score |
9.365633e-07 |
| Marked as misclassified |
No |
| Message-id |
<1311003562.45.0.47024284938.issue1626300@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The original bug is that the distutils docs use commands like "python setup.py spam" all over the place, and they don’t typically work
> because the python executable is not in the path in the default
> install. 'setup.py install' will work since .py files are associated
> with python.exe
(quoted from the first message). I added a note to instruct Windows users to mentally replace those commands with "setup.py spam".
Now my concern is about packaging: In a typical Windows install, can people run "pysetup3 spam"? |
|