Issue 9873: the URL parsing functions now accept ASCII encoded byte sequences in…

Issue 9873: the URL parsing functions now accept ASCII encoded byte sequences in addition to character strings

Doc/whatsnew/3.2.rst

@@ -573,6 +573,14 @@ New, Improved, and Deprecated Modules
   (Contributed by Rodolpho Eckhardt and Nick Coghlan, :issue:`10220`.)
 
 .. XXX: Mention inspect.getattr_static (Michael Foord)
+.. XXX: Mention urllib.parse changes
+          Issue 9873 (Nick Coghlan):
+            - ASCII byte sequence support in URL parsing
+            - named tuple for urldefrag return value
+          Issue 5468 (Dan Mahn) for urlencode:
+            - bytes input support
+            - non-UTF8 percent encoding of non-ASCII characters
+          Issue 2987 for IPv6 (RFC2732) support in urlparse
 
 Multi-threading
 ===============

Misc/NEWS

@@ -43,6 +43,9 @@ Core and Builtins
 Library
 -------
 
+- Issue #9873: The URL parsing functions in urllib.parse now accept
+  ASCII byte sequences as input in addition to character strings.
+
 - Issue #10586: The statistics API for the new functools.lru_cache has
   been changed to a single cache_info() method returning a named tuple.