[Python-Dev] Disabling changing sys.argv[0] with runpy.run_module(...alter_sys=True) (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Mon Feb 22 03:07:45 EST 2016
- Previous message (by thread): [Python-Dev] Disabling changing sys.argv[0] with runpy.run_module(...alter_sys=True)
- Next message (by thread): [Python-Dev] Disabling changing sys.argv[0] with runpy.run_module(...alter_sys=True)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 17 February 2016 at 15:42, Gregory P. Smith <greg at krypto.org> wrote:
sys.argv represents the C main() argv array. Your inclination (in the linked to bug above) to leave sys.argv[0] alone is a good one.
No, it doesn't - it represents the state of argv after CPython's main function is done processing arguments (that's why we have a longstanding RFE requesting the availability of sys.raw_argv)
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160222/d2213158/attachment.html>
- Previous message (by thread): [Python-Dev] Disabling changing sys.argv[0] with runpy.run_module(...alter_sys=True)
- Next message (by thread): [Python-Dev] Disabling changing sys.argv[0] with runpy.run_module(...alter_sys=True)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]