classification
Title: Simplifying os.exec*
Type: enhancement Stage: resolved
Components: Library (Lib) Versions: Python 3.4
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: Sworddragon, r.david.murray
Priority: normal Keywords:

Created on 2015-08-27 07:18 by Sworddragon, last changed 2015-08-27 13:52 by r.david.murray. This issue is now closed.

Messages (2)
msg249224 - (view) Author: (Sworddragon) Date: 2015-08-27 07:18
I'm seeing in the documentation 8 different os.exec* functions that differ only slightly. I think from the way they are differing they could also all be merged into 1 function which could look like this:

os.exec(file, args, env, use_path)

- file is the path to the executable file and if use_path is True the PATH environment variable will be used to look for it (reflects p).
- args will be a dynamic list or tuple of arguments as it can handle a fixed and a variable number of arguments (reflects v).
- env is the mapping of the environment variables which will be used or None if the environment variables of the current process shall be used (reflects e).

env would default to None and use_path either to False or True.
msg249234 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2015-08-27 13:52
The functions in the os module are (for the most part) thin wrappers around OS apis (mostly posix).  The 8 function reflect the posix functions.  If you want a convenience interface, use the subprocess module.
History
Date User Action Args
2015-08-27 13:52:54r.david.murraysetstatus: open -> closed

nosy: + r.david.murray
messages: + msg249234

resolution: rejected
stage: resolved
2015-08-27 07:18:51Sworddragoncreate