[ python-Feature Requests-1379573 ] python executable optionally should search script on PATH
SourceForge.net
noreply at sourceforge.net
Fri Mar 16 07:39:57 CET 2007
Feature Requests item #1379573, was opened at 2005-12-13 07:13
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1379573&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Christoph Conrad (cconrad)
Assigned to: Nobody/Anonymous (nobody)
Summary: python executable optionally should search script on PATH
Initial Comment:
I've seen that with perl - parameter -S means search
script on path. Very helpful.
----------------------------------------------------------------------
>Comment By: Neal Norwitz (nnorwitz)
Date: 2007-03-15 23:39
Message:
Logged In: YES
user_id=33168
Originator: NO
What's the status of this? Is it a bug report?
----------------------------------------------------------------------
Comment By: Christoph Conrad (cconrad)
Date: 2006-02-20 03:10
Message:
Logged In: YES
user_id=21338
(1)
(HKCU|HKLM)\Software\Classes\Python.File\open\command
really is
(HKCU|HKLM)\Software\Classes\Python.File\shell\open\command
(2)
with python 24 a new behaviour occurs: i try to execute the
script on the commandline, but a dialog boy appears with:
the file "[...correct complete path to the script...]" could
not be found. Again, if i prepend python.exe, everything
works as expected. windows 2000 professional.
----------------------------------------------------------------------
Comment By: Georg Brandl (birkenfeld)
Date: 2006-02-20 01:14
Message:
Logged In: YES
user_id=1188172
Do you mean that the registry setting is ok, but the
parameters are not passed correctly?
----------------------------------------------------------------------
Comment By: Christoph Conrad (cconrad)
Date: 2006-02-20 00:12
Message:
Logged In: YES
user_id=21338
I checked the registry. It's ok. It's windows 2000.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2006-01-16 13:29
Message:
Logged In: YES
user_id=21627
That (arguments not passed to the script) was a bug in some
versions of the Windows installer. Please verify that the
registry, at
(HKCU|HKLM)\Software\Classes\Python.File\open\command has
the value '[path]python.exe "%1" %*'. The %* part should
arrange for arguments being passed.
----------------------------------------------------------------------
Comment By: Christoph Conrad (cconrad)
Date: 2006-01-16 02:59
Message:
Logged In: YES
user_id=21338
> On windows, you should be able to just invoke the_script.py
> (i.e. without a preceding python.exe). Does this not work
> for you?
It works - but command line args are not given to the called
script. If i prepend python.exe, command line args are
transferred correctly.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2006-01-14 10:34
Message:
Logged In: YES
user_id=21627
On windows, you should be able to just invoke the_script.py
(i.e. without a preceding python.exe). Does this not work
for you?
----------------------------------------------------------------------
Comment By: Christoph Conrad (cconrad)
Date: 2005-12-15 14:00
Message:
Logged In: YES
user_id=21338
i meant the windows operating system.
----------------------------------------------------------------------
Comment By: Georg Brandl (birkenfeld)
Date: 2005-12-15 13:40
Message:
Logged In: YES
user_id=1188172
I don't know... if the script is in the PATH, isn't it
normally executable too?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1379573&group_id=5470
More information about the Python-bugs-list
mailing list