gh-63293: Deprecate providing false values besides strings or bytes to urllib.parse functions by jacobtylerwalls · Pull Request #26687

gh-63293: Deprecate providing false values besides strings or bytes to urllib.parse functions by jacobtylerwalls · Pull Request #26687 · python/cpython

jacobtylerwalls changed the title ~~bpo-19094: Raise TypeError in urljoin(), urlparse(), and urlsplit() for inappropriate types~~ bpo-19094: Raise TypeError in urllib.parse for inappropriate types

Jun 13, 2021

jacobtylerwalls changed the title ~~bpo-19094: Raise TypeError in urllib.parse for inappropriate types~~ bpo-19094: Raise TypeError in urllib.parse for objects besides strings or bytes

Jun 14, 2021

…t()` for inappropriate types

Co-authored-by: Vajrasky Kok <sky.kok@speaklikeaking.com>

This extends the solution to urldefrag(), urlunparse(), urlunsplit(), and parse_qsl()

jacobtylerwalls changed the title ~~bpo-19094: Raise TypeError in urllib.parse for objects besides strings or bytes~~ bpo-19094: Deprecate providing false values besides strings to urllib.parse functions

Feb 23, 2022

jacobtylerwalls changed the title ~~bpo-19094: Deprecate providing false values besides strings to urllib.parse functions~~ bpo-19094: Deprecate providing false values besides strings or bytes to urllib.parse functions

Feb 23, 2022

jacobtylerwalls changed the title ~~bpo-19094: Deprecate providing false values besides strings or bytes to urllib.parse functions~~ gh-63293: Deprecate providing false values besides strings or bytes to urllib.parse functions

Jun 18, 2022