[3.15] gh-105708: 'V' could be case insensitive for IPvFuture hostnames (GH-105709)#153138
Conversation
pythonGH-105709) * pythongh-105708: 'V' could be case insensitive for IPvFuture hostnames * pythongh-105708: 'V' could be case insensitive for IPvFuture hostnames & checking empty hostnames * 📜🤖 Added by blurb_it. * Fix the Merge changing \z to \Z. * Fixed the News Entry. * Fix the lint. --------- (cherry picked from commit a47a66c) Co-authored-by: Chandra <csreddy1998@gmail.com> Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com> Co-authored-by: Senthil Kumaran <senthil@python.org>
orsenthil
added
needs backport to 3.13
|
Thanks @miss-islington for the PR, and @orsenthil for merging it 🌮🎉.. I'm working now to backport this PR to: 3.15. |
|
Thanks @miss-islington for the PR, and @orsenthil for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
|
Thanks @miss-islington for the PR, and @orsenthil for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
orsenthil
removed
needs backport to 3.13
|
Sorry, @miss-islington and @orsenthil, I could not cleanly backport this to |
|
Sorry, @miss-islington and @orsenthil, I could not cleanly backport this to |
|
Sorry, @miss-islington and @orsenthil, I could not cleanly backport this to |
3 participants
urlparser does not allow 'V' in the IPvFuture. #105708: 'V' could be case insensitive for IPvFuture hostnames
urlparser does not allow 'V' in the IPvFuture. #105708: 'V' could be case insensitive for IPvFuture hostnames & checking empty hostnames
📜🤖 Added by blurb_it.
Fix the Merge changing \z to \Z.
Fixed the News Entry.
Fix the lint.
(cherry picked from commit a47a66c)
Co-authored-by: Chandra csreddy1998@gmail.com
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
Co-authored-by: Senthil Kumaran senthil@python.org