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 ncoghlan
Recipients Arfrever, Ben.Darnell, barry, brett.cannon, danielsh, eric.araujo, flox, georg.brandl, jwilk, ncoghlan, pitrou, rhettinger
Date 2017-03-20.06:34:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489991684.55.0.477633591748.issue14208@psf.upfronthosting.co.za>
In-reply-to
Content
A few updates here:

* For the specific case of `python -m`, the original argument has been available as `__main__.__spec__.name` since Python 3.4

* Also since Python 3.4, the `multiprocessing` module has correctly handled the -m switch. For more details, see https://docs.python.org/3/whatsnew/3.4.html#multiprocessing and the linked issues.

* However, there are still some cases where it is potentially useful to have access to the full details of how the host Python runtime was invoked, rather than just the arguments that were left after CPython's runtime processing was completed. I filed issue 29857 as a new RFE specifically suggesting a `sys._raw_argv` attribute addressing that question.
History
Date User Action Args
2017-03-20 06:34:44ncoghlansetrecipients: + ncoghlan, barry, brett.cannon, georg.brandl, rhettinger, pitrou, jwilk, eric.araujo, Arfrever, flox, Ben.Darnell, danielsh
2017-03-20 06:34:44ncoghlansetmessageid: <1489991684.55.0.477633591748.issue14208@psf.upfronthosting.co.za>
2017-03-20 06:34:44ncoghlanlinkissue14208 messages
2017-03-20 06:34:43ncoghlancreate