René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"pathlib.PureWindowsPath comparison results vary between Windows and Posix","articleBody":"In #31691 I switched `pathlib.PureWindowsPath` comparisons to use `os.path.normcase()` rather than `str.lower()`. This is probably a mistake, as @eryksun [points out](https://github.com/python/cpython/issues/104484#issuecomment-1560419031):\r\n\r\n\u003e The inconsistency is with `ntpath.normcase()` on Windows. It's probably for the best if the pure comparison methods revert to using `str.lower()` for the sake of consistency, not only with `glob()` and `match()`, but also with using `PureWindowsPath` on POSIX. Maybe platform-dependent comparisons could be implemented on `Path`.\r\n\u003e \r\n\u003e On Windows, `ntpath.normcase()` is based on `LCMapStringEx()`. It turns out that this function implements a case mapping for some non-BMP characters. WinAPI [`CompareStringOrdinal()`](https://learn.microsoft.com/en-us/windows/win32/api/stringapiset/nf-stringapiset-comparestringordinal), on the other hand, has no case mapping for non-BMP characters, which is consistent with Microsoft's filesystems. Thus I'd prefer for a platform-dependent comparison to use `CompareStringOrdinal()` instead of `LCMapStringEx()`.\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-104948\n* gh-104990\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/barneygale","@type":"Person","name":"barneygale"},"datePublished":"2023-05-25T21:46:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/104947/cpython/issues/104947"}