Lincoln Auster added the comment:
> In my idea it would not be a list of things that you have to pass
> piecemeal to request specific behaviour, but another function or a new
> param (like `parse(string, universal=True)`) that implements universal
> parsing.
If I'm correct in
Lincoln Auster added the comment:
> Maybe a new parse function, or new parameter to the existing one,
> could be easier to add.
If I'm understanding you right, that's what this (and the PR) is - an
extra optional parameter to urllib.parse to supplement the existing
(legacy?)
Change by Lincoln Auster :
--
keywords: +patch
pull_requests: +28721
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/30520
___
Python tracker
<https://bugs.python.org/issu
New submission from Lincoln Auster :
It looks like this was discussed in 2013-2015 here:
https://bugs.python.org/issue18828
Basically, with all the URL schemes that exist in the world (and the
possibility of a custom scheme), the current strategy of enumerating what do
what in a hard-coded
