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 Susumu Koshiba, deronnax, martin.panter, r.david.murray, spaceone
Date 2016-06-04.00:33:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465000413.89.0.903740263994.issue25738@psf.upfronthosting.co.za>
In-reply-to
Content
Well, the reason it makes sense to use send_error, or at least the reason I suspect a lot of people do it, is because then you don't have to call end_headers() yourself.  So, acknowleding this, it might be worth mentioning in the docs that the body isn't sent for certain return codes.  Especially seeing as we already do it for NO_CONTENT and NOT_MODIFIED.
History
Date User Action Args
2016-06-04 00:33:33r.david.murraysetrecipients: + r.david.murray, martin.panter, deronnax, spaceone, Susumu Koshiba
2016-06-04 00:33:33r.david.murraysetmessageid: <1465000413.89.0.903740263994.issue25738@psf.upfronthosting.co.za>
2016-06-04 00:33:33r.david.murraylinkissue25738 messages
2016-06-04 00:33:33r.david.murraycreate