[issue23082] pathlib relative_to() can give confusing error message

miss-islington added the comment: New changeset 318a18eb889e8733ffb25ada139fdd423606a609 by Miss Islington (bot) in branch '3.9': bpo-23082: Better error message for PurePath.relative_to() from pathlib (GH-19611) https://github.com/python/cpython/commit/318a18eb889e8733ffb25ada139fdd423606a6

[issue23082] pathlib relative_to() can give confusing error message

Change by Steve Dower : -- nosy: -miss-islington resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.10 -Python 3.8 ___ Python tracker ___

[issue23082] pathlib relative_to() can give confusing error message

Steve Dower added the comment: New changeset 448325369ff73011d34d6c3a493014fe3ead8843 by Rotuna in branch 'master': bpo-23082: Better error message for PurePath.relative_to() from pathlib (GH-19611) https://github.com/python/cpython/commit/448325369ff73011d34d6c3a493014fe3ead8843 -

[issue23082] pathlib relative_to() can give confusing error message

Change by miss-islington : -- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +19658 pull_request: https://github.com/python/cpython/pull/20395 ___ Python tracker _

[issue23082] pathlib relative_to() can give confusing error message

Ido Michael added the comment: Hey looks like this PR is good to go? -- nosy: +Ido Michael ___ Python tracker ___ ___ Python-bugs-l

[issue23082] pathlib relative_to() can give confusing error message

Change by Sadhana Srinivasan : -- keywords: +patch pull_requests: +18945 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19611 ___ Python tracker _

[issue23082] pathlib relative_to() can give confusing error message

Sadhana Srinivasan added the comment: I'll work on this. I tried to come up with a single error message but having two different error messages seems like a better idea to me. One for when the path isn't a subpath and one for when absolute and relative paths are mixed. Basically to explain

[issue23082] pathlib relative_to() can give confusing error message

Steve Dower added the comment: I agree it's worth improving the error message (and probably the docs too). It's never made clear that relative_to only looks deeper (won't ever generate leading ".." parts) - the closest hint in the docs is that os.path.relpath is different (and that isn't eve

[issue23082] pathlib relative_to() can give confusing error message

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue23082] pathlib relative_to() can give confusing error message

Changes by Arfrever Frehtes Taifersar Arahesis : -- assignee: -> pitrou nosy: +Arfrever, pitrou ___ Python tracker ___ ___ Python-bug

[issue23082] pathlib relative_to() can give confusing error message

Chris Jerdonek added the comment: By the way, here is another (less) confusing error message: >>> Path("foo").relative_to("fo") Traceback (most recent call last): File "", line 1, in File "/opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/pathlib.py"

[issue23082] pathlib relative_to() can give confusing error message

New submission from Chris Jerdonek: pathlib's relative_to(other) can give a confusing message when "other" is os.curdir. For example-- Python 3.4.2 (default, Nov 12 2014, 18:23:59) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.54)] on darwin Type "help", "copyright", "credits"