➜

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 martin.panter
Recipients docs@python, martin.panter, serhiy.storchaka
Date 2015-03-31.11:50:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1427802639.04.0.473499416414.issue23360@psf.upfronthosting.co.za>
In-reply-to
Content 
I think we should avoid mentioning bytes-like objects until Issue 23740 (http.client support), Issue 23756 (clarify definition), and/or SSLSocket.sendall() support are sorted out.

Changes in non-urlencoded.3.patch:
* Removed iterable object as direct urlopen() argument, since that would require a custom Content-Length and therefore a custom Request object
* Removed Content-Type discussion from urlopen() for similar reasons
* Added iterable object to Request constructor (already tested)
* Clarified default Content-Type whenever data is not None
* Added a test for default Content-Type with iterable object
History
Date User Action Args
2015-03-31 11:50:39martin.pantersetrecipients: + martin.panter, docs@python, serhiy.storchaka
2015-03-31 11:50:39martin.pantersetmessageid: <1427802639.04.0.473499416414.issue23360@psf.upfronthosting.co.za>
2015-03-31 11:50:39martin.panterlinkissue23360 messages
2015-03-31 11:50:38martin.pantercreate