-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
gh-136437: Document some os.path
functions as requiring pos-only
#136812
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a net improvement -- I still have slight reservations about the trailing '/', but we've discussed a couple of mitigations (e.g. in JS). Happy to support this.
A
Thanks @sobolevn for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
…nly (pythonGH-136812) (cherry picked from commit b5428bb) Co-authored-by: sobolevn <mail@sobolevn.me>
…nly (pythonGH-136812) (cherry picked from commit b5428bb) Co-authored-by: sobolevn <mail@sobolevn.me>
GH-136944 is a backport of this pull request to the 3.14 branch. |
GH-136945 is a backport of this pull request to the 3.13 branch. |
@chirizxc reached out to me and asked to take this issue over. So, here's mine PR :)
I scanned through all
os.path
functions that do use different pos-or-keyword parameter name from the documented one. And added/
to them. See #136437 (comment)I plan that we can backport this.
The second PR that I am working on is to actually make these functions pos-only in 3.15
os.path
documentation vs. runtime #136437📚 Documentation preview 📚: https://cpython-previews--136812.org.readthedocs.build/