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 gvanrossum
Recipients docs@python, gvanrossum, jaraco, terry.reedy
Date 2020-08-31.00:02:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJLXfcdWBbPyOTnoeVRDoDGKXNssCPyusmassURUi=JXyg@mail.gmail.com>
In-reply-to <1598826509.94.0.24825884817.issue41615@roundup.psfhosted.org>
Content
Got it.

On Sun, Aug 30, 2020 at 15:28 Terry J. Reedy <report@bugs.python.org> wrote:

>
>
> Terry J. Reedy <tjreedy@udel.edu> added the comment:
>
>
>
> sys.argv cannot be set until sys exists.  As I mentioned above, subsequent
> calls before finalization must continue to be no-ops.
>
>
>
> Code that depends on a bug, in this case of sys.argv not existing, is
> always vulnerable.  In this case, I would expect that people who want
> sys.argv to have a particular value would unconditionally set it.  If it
> were conditionally set, the program would likely exit or otherwise fail a
> test.  I intentionally have not suggested backporting a code change.
>
>
>
> ----------
>
>
>
> _______________________________________
>
> Python tracker <report@bugs.python.org>
>
> <https://bugs.python.org/issue41615>
>
> _______________________________________
>
> --
--Guido (mobile)
History
Date User Action Args
2020-08-31 00:02:18gvanrossumsetrecipients: + gvanrossum, terry.reedy, jaraco, docs@python
2020-08-31 00:02:18gvanrossumlinkissue41615 messages
2020-08-31 00:02:17gvanrossumcreate