➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients Mike.Lissner, gregory.p.smith, orsenthil, serhiy.storchaka, vstinner, xtreak
Date 2021-05-05.01:34:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1620178466.51.0.788528540569.issue43883@roundup.psfhosted.org>
In-reply-to
Content 
FWIW rather than implementing our own URL parsing at all... wrapping a library extracted from a compatible-license major browser (Chromium or Firefox) and keeping it updated would avoid disparities.

Unfortunately, I'm not sure how feasible this really is.  Do all of the API surfaces we must support in the stdlib for compatibility's sake with urllib line up with such a browser core URL parsing library?

Something to ponder.  Unlikely something we'll actually do.
History
Date User Action Args
2021-05-05 01:34:26gregory.p.smithsetrecipients: + gregory.p.smith, orsenthil, vstinner, serhiy.storchaka, Mike.Lissner, xtreak
2021-05-05 01:34:26gregory.p.smithsetmessageid: <1620178466.51.0.788528540569.issue43883@roundup.psfhosted.org>
2021-05-05 01:34:26gregory.p.smithlinkissue43883 messages
2021-05-05 01:34:26gregory.p.smithcreate