Message179855
| Author |
ncoghlan |
| Recipients |
Arfrever, Ben.Darnell, brett.cannon, danielsh, eric.araujo, flox, georg.brandl, ncoghlan, pitrou, rhettinger |
| Date |
2013年01月13日.10:16:28 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1358072189.06.0.44115031601.issue14208@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I'm not seeing a good justification for doing anything more, though:
- needing to access this information is an exceedingly niche use case
- I don't see any way for raw_argv to be useful in a cross-implementation manner.
- the exposure as sys._configuration.raw_argv is a natural consequence of the PEP 432 implementation (it's there to allow an embedding application to override the command line arguments seen by CPython)
Elevating it to part of the language standard doesn't make sense, while exposing it as an implementation feature of the CPython initialisation process seems more reasonable. |
|