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.

Author Sworddragon
Recipients Sworddragon
Date 2015-08-27.07:18:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440659931.7.0.364118068973.issue24943@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2015-08-27 07:18:51Sworddragonsetrecipients: + Sworddragon
2015-08-27 07:18:51Sworddragonsetmessageid: <1440659931.7.0.364118068973.issue24943@psf.upfronthosting.co.za>
2015-08-27 07:18:51Sworddragonlinkissue24943 messages
2015-08-27 07:18:50Sworddragoncreate