Thanks for the review!

Perhaps you could add a note that users may wish to only call it with resolved / normalised / casefolded / etc paths, and provide a brief sketch of doing so?

It's hard to give good advice, because there are several edge cases that may or may not be relevant depending on user need.resolve() only emulates (perhaps imperfectly) what the OS does to resolve paths, and there's a TOC/TOU thing because someone could swap a symlink target in the path immediately after you call it.

(tbh I'd ratheris_relative_to() didn't exist, but we're here now)

I think the actual change here is fine to merge -- the comment was just the cherry on top, but it would simply add confusion then best avoided -- and the reader can infer that no path processing is done from the current text as proposed.

A

Thanks again!

Thanks@barneygale for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12.
🐍🍒⛏🤖

Sorry,@barneygale, I could not cleanly backport this to3.11 due to a conflict.
Please backport usingcherry_picker on command line.

cherry_picker 3a61d24062aaa1e13ba794360b6c765d9a1f2b06 3.11

GH-114460 is a backport of this pull request to the3.12 branch.

GH-114461 is a backport of this pull request to the3.11 branch.