[issue43883] Making urlparse WHATWG conformant

Gregory P. Smith added the comment: 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.

[issue43883] Making urlparse WHATWG conformant

Change by Gregory P. Smith : -- nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43883] Making urlparse WHATWG conformant

STINNER Victor added the comment: See also bpo-43882. -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue43883] Making urlparse WHATWG conformant

Change by Mike Lissner : -- nosy: +Mike.Lissner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43883] Making urlparse WHATWG conformant

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43883] Making urlparse WHATWG conformant

Serhiy Storchaka added the comment: It would be interesting to test also with the yarl module. It is based on urlparse and urljoin, but does extra normalization of %-encoding. -- nosy: +serhiy.storchaka ___ Python tracker

[issue43883] Making urlparse WHATWG conformant

New submission from Senthil Kumaran : Mike Lissner reported that a set test suites that exercise extreme conditions with URLs, but in conformance with url.spec.whatwg.org was maintained here: https://github.com/web-platform-tests/wpt/tree/77da471a234e03e65a22ee6df8ceff7aaba391f8/url These