[issue37969] urllib.parse functions reporting false equivalent URIs

Géry added the comment: @nicktimko Thanks for the historical track. Here is a patch that solves this issue by updating the `urlsplit` and `urlunsplit` functions of the `urllib.parse` module to keep the '?' and '#' delimiters in URIs if present, even if their associated component is empty, as

[issue37969] urllib.parse functions reporting false equivalent URIs

Change by Géry : -- keywords: +patch pull_requests: +15308 stage: -> patch review pull_request: https://github.com/python/cpython/pull/15642 ___ Python tracker ___

[issue37969] urllib.parse functions reporting false equivalent URIs

Nick Timkovich added the comment: Looking at the history, the line in the docs used to say > ... (for example, an empty query (the draft states that these are equivalent). which was changed to "the RFC" in April 2006

[issue37969] urllib.parse functions reporting false equivalent URIs

New submission from Géry : The Python library documentation of the `urllib.parse.urlunparse `_ and `urllib.parse.urlunsplit `_ functions