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 r.david.murray
Recipients docs@python, jugglinmike, r.david.murray
Date 2017-04-25.14:58:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493132334.02.0.355639796065.issue30160@psf.upfronthosting.co.za>
In-reply-to
Content
I would like to say that the latter interpretation is "obviously" correct, except that it clearly wasn't obvious to you.  The fact that it "contains the output stream" I would have thought was pretty clear: if you are writing to it, you are responsible for anything you do to that output stream.  The "must" refers to the same the the RFC "must" refers to: in order to be RFC compliant, you must conform to the RFC.

Perhaps we could clarify that sentence by saying: "Proper adherence to the HTTP protocol must be used when writing to this stream in order to achieve successful interoperation with http clients."  I think that would make it clear that if you don't, you'll be testing the client's response to protocol violations :)
History
Date User Action Args
2017-04-25 14:58:54r.david.murraysetrecipients: + r.david.murray, docs@python, jugglinmike
2017-04-25 14:58:54r.david.murraysetmessageid: <1493132334.02.0.355639796065.issue30160@psf.upfronthosting.co.za>
2017-04-25 14:58:53r.david.murraylinkissue30160 messages
2017-04-25 14:58:53r.david.murraycreate