Author martin.panter
Recipients eric.araujo, ezio.melotti, martin.panter, nadeem.vawda, orsenthil, petri.lehtinen, sandro.tosi
Date 2015-01-29.04:44:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422506686.28.0.055688227957.issue12707@psf.upfronthosting.co.za>
In-reply-to
Content
I think it would be okay to deprecate the methods in the documentation, but they should not be removed nor trigger warnings any time soon.

Currently the following related methods and attributes are documented:

* addinfourl.getcode() == HTTPResponse.status == HTTPError.code
* HTTPResponse.reason == HTTPError.reason (HTTPError documentation is vague on this.)
* addinfourl.geturl()
* addinfourl.info() == HTTPResponse.msg == HTTPError.headers (But see Issue 22989 and patch in Issue 21228 for a quirk with HTTPResponse.)

It would be nice to ensure these three classes all implement the same “Response” interface, except that geturl() and “url” may not be appropriate for HTTPResponse. The “code” and “headers” attributes should definitely be documented for consistency. I propose also adding and documenting “reason”.
History
Date User Action Args
2015-01-29 04:44:46martin.pantersetrecipients: + martin.panter, orsenthil, nadeem.vawda, ezio.melotti, eric.araujo, sandro.tosi, petri.lehtinen
2015-01-29 04:44:46martin.pantersetmessageid: <1422506686.28.0.055688227957.issue12707@psf.upfronthosting.co.za>
2015-01-29 04:44:46martin.panterlinkissue12707 messages
2015-01-29 04:44:46martin.pantercreate