Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #83133
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Subject | Re: Command Line Inputs from Windows |
| Date | 2015-01-02 16:30 -0500 |
| Organization | IISS Elusive Unicorn |
| References | <COL130-DS1607D96864155F77FE9C11C85D0@phx.gbl> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.17335.1420234238.18130.python-list@python.org> (permalink) |
On Fri, 2 Jan 2015 12:44:55 -0700, "Ken Stewart"
<gordon_ken_stewart@msn.com> declaimed the following:
>
>The Windows PATH environment variable contains the path to Python, as well
>as the path to the Script directory. The PATHEXT environment variable
>contains the Python extension (.py).
>
Unfortunately, this is more a matter of the registry -- and there are
half a dozen possible registry keys that may exist depending upon which
version of Python had been installed, which OS it is on, and whether as
admin or local user...
A starting point may be:
http://stackoverflow.com/questions/2640971/windows-is-not-passing-command-line-arguments-to-python-programs-executed-from-t
though I'd recommend doing a registry search for anything that looks like a
Python command line invocation (mine were under Python.File for example).
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Command Line Inputs from Windows Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-01-02 16:30 -0500
csiph-web