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 ncoghlan
Recipients Mike.Lissner, demian.brecht, ezio.melotti, ncoghlan, orsenthil, pitrou
Date 2014-08-10.23:38:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7f7==J7qZCBOyNasuP_ojWx0FNcH3o639fX74eOkqN4yw@mail.gmail.com>
In-reply-to <1407685856.3.0.317263445241.issue22118@psf.upfronthosting.co.za>
Content
Unfortunately, I haven't looked at the RFC compliance side of things in
this space in years. At the time, we were considering a new module, leaving
the old one alone.

These days, I'd be more inclined to just fix it for 3.5, and suggest anyone
really needing the old behaviour fork an older version of the module.

Extracting the test case inputs from that old "uriparse" rewrite might
still be a good idea, though.
History
Date User Action Args
2014-08-10 23:38:13ncoghlansetrecipients: + ncoghlan, orsenthil, pitrou, ezio.melotti, demian.brecht, Mike.Lissner
2014-08-10 23:38:13ncoghlanlinkissue22118 messages
2014-08-10 23:38:13ncoghlancreate