[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

Steve Dower added the comment: New changeset 9c5fa9c97c5c5336e60e4ae7a2e6e3f67acedfc7 by neonene in branch 'main': bpo-46208: Fix normalization of relative paths in _Py_normpath()/os.path.normpath (GH-30362) https://github.com/python/cpython/commit/9c5fa9c97c5c5336e60e4ae7a2e6e3f67acedfc7

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

Steve Dower added the comment: I'm happy with PR 30362 now - any other comments before we merge? -- ___ Python tracker ___ ___ Pyth

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

neonene added the comment: >Here's a branch with a passing ntpath.normpath test and a failing >posixpath.normpath test: I took the test cases for my PR, thanks. On Windows machine, ntpath fails and posixpath passes. It seems that the passing one is tested with pure python code. --

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

Change by neonene : -- keywords: +patch nosy: +neonene nosy_count: 3.0 -> 4.0 pull_requests: +28576 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30362 ___ Python tracker __

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

Hugo van Kemenade added the comment: Here's a branch with a passing ntpath.normpath test and a failing posixpath.normpath test: https://github.com/hugovk/cpython/tree/issue-46208-tests https://github.com/hugovk/cpython/commit/d7e8da179adce51a8f63d2dbd062a272dda826bc --

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

Steve Dower added the comment: Yep, it's a bug and should be fixed. I'm still not back coding yet, but I'll get to it once I am if nobody else gets there first. This is going to affect getpath.py in the native implementation, so it ought to be fixed there (and we need tests for this case, si

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

Hugo van Kemenade added the comment: git bisect between v3.11.0a2 and v3.11.0a3 points to the same commit, 99fcf1505218464c489d419d4500f126b6d6dc28. -- ___ Python tracker ___

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

Christian Heimes added the comment: The issue could be related to 99fcf1505218464c489d419d4500f126b6d6dc28 / bpo-45582. -- nosy: +christian.heimes, steve.dower ___ Python tracker ___

[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+

New submission from Hugo van Kemenade : The behaviour of os.path.normpath appears to have changed between Python 3.10/Python 3.11.0a2 and 3.11.0a3+. I don't see anything mentioned in https://docs.python.org/3.11/whatsnew/3.11.html Is this intentional? Old behaviour: Python 3.10.1 (v3.10.1