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 mgiuca
Recipients brett.cannon, draghuram, dyoo, facundobatista, hdiogenes, mgiuca, orsenthil
Date 2008-08-25.09:44:11
SpamBayes Score 0.00020564212
Marked as misclassified No
Message-id <1219657453.26.0.268831527623.issue600362@psf.upfronthosting.co.za>
In-reply-to
Content
It seems like parse_multipart and parse_header are very strongly related
to parse_qs. (eg. if you want to process HTTP requests you'll want to
call parse_qs for x-www-form-urlencoded and parse_multipart for
multipart/form-data).

Should these be moved too? (They aren't part of the url syntax though,
so it doesn't make sense for them to be in urlparse).
History
Date User Action Args
2008-08-25 09:44:13mgiucasetrecipients: + mgiuca, facundobatista, dyoo, orsenthil, draghuram, hdiogenes, bcannon.historic
2008-08-25 09:44:13mgiucasetmessageid: <1219657453.26.0.268831527623.issue600362@psf.upfronthosting.co.za>
2008-08-25 09:44:12mgiucalinkissue600362 messages
2008-08-25 09:44:12mgiucacreate