René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Minor parsing issue with new -X int_max_str_digits option if PYTHONINTMAXSTRDIGITS","articleBody":"``python -X int_max_str_digits`` command is invalid:\r\n\r\n```\r\n$ python -X int_max_str_digits\r\nFatal Python error: config_init_int_max_str_digits: -X int_max_str_digits: invalid limit; must be \u003e= 640 or 0 for unlimited.\r\nPython runtime state: preinitialized\r\n```\r\n\r\nBut if PYTHONINTMAXSTRDIGITS environment variable is defined, the invalid option is no longer rejected:\r\n\r\n```\r\n$ PYTHONINTMAXSTRDIGITS=5000 python -X int_max_str_digits\r\nPython 3.12.0a0 (heads/main:e37ac5fbb6, Sep 15 2022, 15:03:41) [GCC 12.2.1 20220819 (Red Hat 12.2.1-1)] on linux\r\nType \"help\", \"copyright\", \"credits\" or \"license\" for more information.\r\n\u003e\u003e\u003e \r\n```\r\n\r\nIt's just because the `valid` variable in config_init_int_max_str_digits() is not initialized again in the -X option code path, after the env var is parsed.\r\n\r\nI noticed this minor issue while backporting the change to Python 3.6 in Fedora for Red Hat.\r\n\r\ncc @tiran @gpshead ","author":{"url":"https://github.com/vstinner","@type":"Person","name":"vstinner"},"datePublished":"2022-09-15T13:10:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/96848/cpython/issues/96848"}