-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
pathlib: move 'resolve()' logic out of path flavour #87923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Under-the-hood functionality in pathlib is divided between:
The '_WindowsFlavour/_PosixFlavour.resolve()' function is misplaced, as it requires OS calls such as In preparation for addressing bpo-24132 I'd like to get these interfaces really tidy. Once bpo-39899 is fixed, this will be the last remaining flavour method that does accessor-y things. |
I'm happy with the PR as it stands now. Anyone else have an opinion? |
pathlib.Path.resolve()
returns an absolute path. (GH-26184) #26270Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: