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 demian.brecht, jimr, martin.panter, orsenthil, r.david.murray
Date 2015-03-02.17:41:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425318075.44.0.984104568378.issue23539@psf.upfronthosting.co.za>
In-reply-to
Content
Not to get into an API argument, but rather to convey some Python philosophy as I understand it: there *is* often a distinction in Python between the value 'None' and a boolean-False-value like ''.  It is often the case in Python APIs that None means something different from other arguably-semantically-equivalent values.  In this case I believe it is entirely logical that 'None' (the default value) for a method that does not normally take a body and makes a distinction based on Content-Length (or some other header) makes sense, and that explicitly saying "I want an empty body, including the standard headers" is actually a sensible Python API.  If we were designing it from scratch with these issues in mind, we might well come up with exactly what we've got...or we might not, because wanting to specify an empty body on such a command is a really low probability event :)

Regardless, we're constrained by backward compatibility here, so the question is moot.
History
Date User Action Args
2015-03-02 17:41:15r.david.murraysetrecipients: + r.david.murray, orsenthil, martin.panter, demian.brecht, jimr
2015-03-02 17:41:15r.david.murraysetmessageid: <1425318075.44.0.984104568378.issue23539@psf.upfronthosting.co.za>
2015-03-02 17:41:15r.david.murraylinkissue23539 messages
2015-03-02 17:41:15r.david.murraycreate