Author martin.panter
Recipients ezio.melotti, martin.panter
Date 2015-10-19.10:34:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445250855.66.0.611879820907.issue25439@psf.upfronthosting.co.za>
In-reply-to
Content
Type checking on the URL should be reasonably straightforward.

For the request data, the question is what types do we currently support? This may be a can of worms. We would have to be careful not to break existing use cases, even undocumented ones.

Looking at Issue 23740, the underlying “http.client” accepts a variety of data types (bytes, Latin-1 str, iterables, files), and this support varies depending if the Content-Length header is supplied. I don’t think all combinations work with urlopen(), but judging by Issue 5038, there is at least partial support for bytes-like, iterables, and file objects.
History
Date User Action Args
2015-10-19 10:34:15martin.pantersetrecipients: + martin.panter, ezio.melotti
2015-10-19 10:34:15martin.pantersetmessageid: <1445250855.66.0.611879820907.issue25439@psf.upfronthosting.co.za>
2015-10-19 10:34:15martin.panterlinkissue25439 messages
2015-10-19 10:34:15martin.pantercreate