[issue1626300] 'Installing Python Modules' does not work for Windows

Éric Araujo added the comment: I consider documentation for the py launched a distinct issue. The original complaint here was fixed, the part about packaging does not apply anymore, so I will close this. If one of the changed instructions still does not work (e.g. “setup.py build” does not w

[issue1626300] 'Installing Python Modules' does not work for Windows

Terry J. Reedy added the comment: I consider it Éric's decision. 3.3 on Windows comes with the new py launcher. That might be incorporated into the docs if it has not. That might also be a separate issue. -- ___ Python tracker

[issue1626300] 'Installing Python Modules' does not work for Windows

Mark Lawrence added the comment: Is any more work needed on this issue or can it be closed? -- nosy: +BreamoreBoy ___ Python tracker ___ ___

[issue1626300] 'Installing Python Modules' does not work for Windows

Terry J. Reedy added the comment: On my fresh install, double clicking *does* run the file as it should, but the window disappears immediately, erasing output and error tracebacks, unless one adds something like ``input("Hit Enter to quit") at the end of the script so the user can see any out

[issue1626300] 'Installing Python Modules' does not work for Windows

Roundup Robot added the comment: New changeset e9022dc7a411 by Éric Araujo in branch '2.7': Remove obsolete term + indicate how to find the program (#1626300). http://hg.python.org/cpython/rev/e9022dc7a411 -- ___ Python tracker

[issue1626300] 'Installing Python Modules' does not work for Windows

Roundup Robot added the comment: New changeset 59f7bbe1236c by Éric Araujo in branch '3.2': Remove obsolete term + indicate how to find the program (#1626300). http://hg.python.org/cpython/rev/59f7bbe1236c New changeset adaec1a0dd47 by Éric Araujo in branch '3.2': Fix instance I missed in 59f7b

[issue1626300] 'Installing Python Modules' does not work for Windows

Terry J. Reedy added the comment: I do not know why the msi installer *silently* fails to properly register extensions even when I leave that checked, or how common that it. I have never looked into the issue more because for development, I prefer to run from an IDLE window and be dumped into

[issue1626300] 'Installing Python Modules' does not work for Windows

Terry J. Reedy added the comment: I believe I meant that 'python setup' works when the script is named 'setup'. Which is to say, python does not require scripts to have an extension, as someone had thought in writing a patch. -- ___ Python tracker

[issue1626300] 'Installing Python Modules' does not work for Windows

Jason R. Coombs added the comment: > > Script run without extensions when run with an explicit python > > command. > Like “python.exe setup” when the file really is setup.py? I’d > never have guessed that. No. Python.exe expects the full path. The only way to execute scripts without the exten

[issue1626300] 'Installing Python Modules' does not work for Windows

Changes by Éric Araujo : -- nosy: +jason.coombs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue1626300] 'Installing Python Modules' does not work for Windows

Éric Araujo added the comment: > Windows file associations are so disfunctional that you should not > depend on them being anything in particular. Ah. Do you think I should revert the change I did for distutils docs to recommend running “setup.py spam”? I followed the opinion of the original

[issue1626300] 'Installing Python Modules' does not work for Windows

Chris Lambacher added the comment: > I am not sure of the difference between 'local script' and 'global command' local script is the setup.py (or for that matter any other script in an arbitrary place in the filesystem. Global command is referring to something installed in %PYTHONINSTALLDIR%\

[issue1626300] 'Installing Python Modules' does not work for Windows

Chris Lambacher added the comment: > Now my concern is about packaging: In a typical Windows install, can people > run “pysetup3 spam”? The windows installer does not make any additions to the path so it is unlikely that "pysetup3 spam" will work. There is http://www.python.org/dev/peps/pep-

[issue1626300] 'Installing Python Modules' does not work for Windows

Terry J. Reedy added the comment: I went back and reread from the beginning, instead of merely answering the question you asked when adding me as nosy. More comments: Windows file associations are so disfunctional that you should not depend on them being anything in particular. I nearly alway

[issue1626300] 'Installing Python Modules' does not work for Windows

Éric Araujo added the comment: 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 as

[issue1626300] 'Installing Python Modules' does not work for Windows

Terry J. Reedy added the comment: I perhaps misunderstood your question. I ran files from the command line as as 'python whatever', not 'whatever' so only python would care about an extension. I do not have a file association to 'run' a file, with or without .py. I presume IDLE does same when

[issue1626300] 'Installing Python Modules' does not work for Windows

Chris Lambacher added the comment: I don't think that is the default state. You need to add .py to the PATHEXT environment variable: http://effbot.org/pyfaq/how-do-i-make-python-scripts-executable.htm Maybe Terry did this at some point? My windows box certainly does not have it and I have 2.6

[issue1626300] 'Installing Python Modules' does not work for Windows

Éric Araujo added the comment: > On Windows, scripts run with whatever name -- no extension or other > extensions. Thanks, this means that the docs can continue to say just “pysetup3”, without “.py”. (I wonder how Windows manages to run the script without file extension!) > I have tested this

[issue1626300] 'Installing Python Modules' does not work for Windows

Terry J. Reedy added the comment: On Windows, scripts run with whatever name -- no extension or other extensions. I have tested this from both IDLE and command line. -- ___ Python tracker __

[issue1626300] 'Installing Python Modules' does not work for Windows

Éric Araujo added the comment: In distutils docs, I’ve mentioned “setup.py thing” as an alternative to “python setup.py thing” on Windows. For packaging, the situation is different: there is no local script anymore, people will have to invoke the global pysetup command. Would it work if I a

[issue1626300] 'Installing Python Modules' does not work for Windows

Éric Araujo added the comment: This is now fixed in the distutils Installing and Distributing guides. Does the same problem apply to the new docs using packaging and the pysetup script? Please check http://docs.python.org/dev/packaging and http://docs.python.org/dev/install -- ___

[issue1626300] 'Installing Python Modules' does not work for Windows

Roundup Robot added the comment: New changeset 072dbebaa83b by Éric Araujo in branch '3.2': Add examples that work on Windows to distutils docs (#1626300) http://hg.python.org/cpython/rev/072dbebaa83b -- ___ Python tracker

[issue1626300] 'Installing Python Modules' does not work for Windows

Roundup Robot added the comment: New changeset 2951641faed1 by Éric Araujo in branch '2.7': Add examples that work on Windows to distutils docs (#1626300) http://hg.python.org/cpython/rev/2951641faed1 -- nosy: +python-dev ___ Python tracker

[issue1626300] 'Installing Python Modules' does not work for Windows

Éric Araujo added the comment: My personal taste is that there is virtue in having such simple examples uncluttered by OS-specific variations, but since MvL does not want the python executable to be on the PATH per default, I defer to him and accept your solution. I’ll make a patch with a sli

[issue1626300] 'Installing Python Modules' does not work for Windows

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue1626300] 'Installing Python Modules' does not work for Windows

Changes by Florent Xicluna : -- assignee: -> d...@python components: +Windows nosy: +d...@python ___ Python tracker ___ ___ Python-

[issue1626300] 'Installing Python Modules' does not work for Windows

Changes by Terry J. Reedy : -- versions: -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue1626300] 'Installing Python Modules' does not work for Windows

Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue1626300] 'Installing Python Modules' does not work for Windows

Changes by Daniel Diniz : -- keywords: +patch nosy: +ajaksu2 stage: -> needs patch type: -> feature request versions: +Python 2.6, Python 3.1 ___ Python tracker ___ _