-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
Correct the description of the 3.7 change in urllib.parse.quote #17065
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
`~` is now treated as an unreserved character (i.e. it doesn't get quoted), not a reserved one.
Thanks for your time @SpecLad, and welcome to CPython! |
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.
This looks good to me! Verified at: https://tools.ietf.org/html/rfc3986#section-2.3
Thanks @SpecLad for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8. |
GH-17229 is a backport of this pull request to the 3.8 branch. |
…onGH-17065) `~` is now treated as an unreserved character (i.e. it doesn't get quoted), not a reserved one. (cherry picked from commit f49f6ba) Co-authored-by: Роман Донченко <dpb@corrigendum.ru>
GH-17230 is a backport of this pull request to the 3.7 branch. |
Congrats on your first CPython contribution @SpecLad! 🍾 Looking forward to seeing more from you in the future. |
…onGH-17065) `~` is now treated as an unreserved character (i.e. it doesn't get quoted), not a reserved one.
…onGH-17065) `~` is now treated as an unreserved character (i.e. it doesn't get quoted), not a reserved one.
~
is now treated as an unreserved character (i.e. it doesn't get quoted), not a reserved one.Automerge-Triggered-By: @taleinat