➜

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.

classification
Title: os.exec* and first 'arg'
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: aschmolck, georg.brandl
Priority: normal Keywords:

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

Messages (2)
msg19044 - (view) Author: Alexander Schmolck (aschmolck) Date: 2003-11-19 19:30 
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
msg19045 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2005-12-26 23:31 
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.
History
Date User Action Args
2022-04-11 14:56:01adminsetgithub: 39569
2003-11-19 19:30:32aschmolckcreate