This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Argument passing from /usr/bin/idle2.3 to
Type: Stage:
Components: None Versions:
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: jafo Nosy List: jafo, kbk, virtualspirit
Priority: normal Keywords: patch

Created on 2003-11-30 06:27 by virtualspirit, last changed 2022-04-11 14:56 by admin. This issue is now closed.

File name Uploaded Description Edit
idle2.3.patch virtualspirit, 2003-11-30 06:27 Adds $*
Messages (6)
msg44963 - (view) Author: Humberto Diógenes (virtualspirit) Date: 2003-11-30 06:27
/usr/bin/idle2.3 wrapper (from the 2.3.2-1pydotorg rpm) ignores 
command-line arguments when calling Fixed only by adding 
"$*" to the script.
msg44964 - (view) Author: Kurt B. Kaiser (kbk) * (Python committer) Date: 2004-12-20 20:53
Logged In: YES 

Appears to be an issue with the Tools section of 
Backport to release23-maint

Assigning to Sean Reifschneider
msg44965 - (view) Author: Sean Reifschneider (jafo) * (Python committer) Date: 2004-12-21 02:25
Logged In: YES 

I went ahead and turned this into Python code and called
"execvp", passing the command arguments onto the idle call.
 This way there are no worries about how the shell handles
$* expansion.  The current CVS version results in something
looking like:

#!/usr/bin/env python2.4
import os, sys
os.execvp("/usr/bin/python2.4", ["/usr/bin/python2.4",
"/usr/lib/python2.4/idlelib/"] + sys.argv[1:])
print "Failed to exec Idle"

(assuming default build settings)
msg44966 - (view) Author: Kurt B. Kaiser (kbk) * (Python committer) Date: 2004-12-22 18:15
Logged In: YES 

This really ought to get into release24-maint and probably
release23-maint if you think anyone will ever build an rpm
from 2.3.5 (which is due out soon).
msg44967 - (view) Author: Sean Reifschneider (jafo) * (Python committer) Date: 2005-01-04 04:05
Logged In: YES 

I've tried checking out python23-maint, but the resulting
tree I'm getting has the latest .spec file.  I can make the
changes to 2.3, but I need some help on how to get a tree I
can check in against, or if I should submit patches to the
msg44968 - (view) Author: Sean Reifschneider (jafo) * (Python committer) Date: 2005-01-05 15:56
Logged In: YES 

mwh helped me get the right check-out of the maintenance
releases.  I've committed these changes to the 2.3 and 2.4
maintenance branches.
Date User Action Args
2022-04-11 14:56:01adminsetgithub: 39632
2003-11-30 06:27:55virtualspiritcreate