René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"os.path.normpath truncates input on null bytes in 3.11, but not 3.10","articleBody":"# Bug report\r\n\r\nLooks like `posix._path_normpath` has slightly different behaviour to the python implementation of `normpath` defined in `posixpath`, as such `os.path.normpath` behaves differently on Python 3.11 (where `posix._path_normpath` is used if it exists) vs 3.10 on posix systems:\r\n\r\nPython 3.10:\r\n```python\r\n\u003e\u003e\u003e import os.path\r\n\u003e\u003e\u003e os.path.normpath('hello\\x00world')\r\n'hello\\x00world'\r\n\u003e\u003e\u003e os.path.normpath('\\x00hello')\r\n'\\x00hello'\r\n```\r\n\r\nPython 3.11:\r\n```python\r\n\u003e\u003e\u003e import os.path\r\n\u003e\u003e\u003e os.path.normpath('hello\\x00world')\r\n'hello'\r\n\u003e\u003e\u003e os.path.normpath('\\x00hello')\r\n'.'\r\n```\r\n\r\nObviously filepaths shouldn't have nulls in them, but the above means invalid input to a program could result in the wrong files or directories being used, rather than an error about embedded nulls once the filepaths are actually used for a system call. And I'm guessing the inconsistency between Python3.10 and 3.11, or between the Python and C implementations of `normpath` was not intended in any case.\r\n\r\n# Your environment\r\n\r\nCPython 3.11.3, running on Arch Linux\r\n\r\nPython 3.11.3 (main, Jun  5 2023, 09:32:32) [GCC 13.1.1 20230429] on linux\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-106816\n* gh-107981\n* gh-107982\n* gh-107983\n* gh-108248\n* gh-108251\n* gh-108252\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/chrisjbillington","@type":"Person","name":"chrisjbillington"},"datePublished":"2023-06-29T12:51:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/106242/cpython/issues/106242"}