bpo-38453: Ensure ntpath.realpath correctly resolves relative paths#16967
Conversation
|
@eryksun Would love your input on this one if you get a chance. |
…flect simplified resolution.
|
Okay, the latest push changes how we handle relative symlink targets. Only things reporting This will change the result for broken links, as we can see in the test updates. It shouldn't affect links that exist, other than fixing the relative path issues we were seeing that were the cause of the bug in the first place (the new |
|
Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
|
Sorry, @zooba, I could not cleanly backport this to |
|
Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
|
Sorry @zooba, I had trouble checking out the |
|
Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
|
Sorry, @zooba, I could not cleanly backport this to |
…ythonGH-16967) Ensure isabs() is always True for \\?\ prefixed paths Avoid unnecessary usage of readlink() to avoid resolving broken links incorrectly Ensure shutil tests run in test directory
|
GH-17174 is a backport of this pull request to the 3.8 branch. |
…H-16967) Ensure isabs() is always True for \\?\ prefixed paths Avoid unnecessary usage of readlink() to avoid resolving broken links incorrectly Ensure shutil tests run in test directory
…ythonGH-16967) Ensure isabs() is always True for \\?\ prefixed paths Avoid unnecessary usage of readlink() to avoid resolving broken links incorrectly Ensure shutil tests run in test directory
…ythonGH-16967) Ensure isabs() is always True for \\?\ prefixed paths Avoid unnecessary usage of readlink() to avoid resolving broken links incorrectly Ensure shutil tests run in test directory
https://bugs.python.org/issue38453