René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`\\r`s introduced after codec decoding cause `SystemError`","articleBody":"# Bug report\n\n### Bug description:\n\n[Found by OSS-Fuzz](https://issues.oss-fuzz.com/issues/464230016).\n\nThe testcase is:\n\n```py\n#coding=U7+AA0''\n```\n\nresulting in:\n\n```\n$ ./python -c \"import py_compile; py_compile.compile('testcase')\"\nSorry: SystemError: Parser/string_parser.c:286: bad argument to internal function\n```\n\nI gather this is because `+AA0` decodes to `\\r` in UTF-7, however, `_PyTokenizer_translate_newlines` is called before the codec decoding so it slips by and blows up (at least it apologizes😆). I think it could be fixed by calling `_PyTokenizer_translate_newlines` again after decoding if a `\\r` is introduced, WDYT?\n\ncc @lysnikolaou @pablogsal \n\n### CPython versions tested on:\n\nCPython main branch\n\n### Operating systems tested on:\n\n_No response_\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-145276\n* gh-145281\n* gh-145310\n* gh-145312\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/StanFromIreland","@type":"Person","name":"StanFromIreland"},"datePublished":"2026-02-25T21:25:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/145234/cpython/issues/145234"}