[ python-Bugs-845342 ] os.exec* and first 'arg'

SourceForge.net noreply at sourceforge.net
Tue Dec 27 00:31:57 CET 2005


Bugs item #845342, was opened at 2003-11-19 20:30
Message generated for change (Comment added) made by birkenfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=845342&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: Documentation
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Alexander Schmolck (aschmolck)
Assigned to: Nobody/Anonymous (nobody)
Summary: os.exec* and first 'arg'

Initial Comment:
The current 

I'd suggest the following change to the docstrings for
the exec* functions, because I think it's quite easy to
get bitten:

execv(...)
    execv(path, args)
    
    Execute an executable path with arguments,
replacing current process.
    
            path: path of executable file
            args: tuple or list of strings (NOTE: the
first argument is
                     analoguous to sys.argv[0], *not*
sys.argv[1]!)

instead of:

execv(...)
    execv(path, args)
    
    Execute an executable path with arguments,
replacing current process.
    
            path: path of executable file
            args: tuple or list of strings



----------------------------------------------------------------------

>Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-12-27 00:31

Message:
Logged In: YES 
user_id=1188172

This is covered in the Library Manual.
Docstrings aren't meant to be complete, just quick overviews
of what the functions do.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=845342&group_id=5470


More information about the Python-bugs-list mailing list