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 EvensF
Recipients EvensF, docs@python, martin.panter, orsenthil, r.david.murray
Date 2014-09-10.19:51:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Well, there wasn't any indication before that the returned object was implementing the "addinfourl" interface. So I don't think we have lost anything. In what situation this interface is useful ? The following comment (that you had highlighted in your comment) gives the impression that theses methods are there only to provide compatibility with clients using old-styles responses.

That would imply that newer clients would usually not use these methods. If you want to document this, I think the "addinfourl" interface should then be better described somewhere else where it would include the fact that the HTTPResponse class implements it.

Anyway, I don't see the advantage of using a getter method (like geturl()) instead of accessing directly the attribute. For me, this is less pythonic. If you ever have to attach a behaviour to the access of this attribute, a property could then be defined.
Date User Action Args
2014-09-10 19:51:11EvensFsetrecipients: + EvensF, orsenthil, r.david.murray, docs@python, martin.panter
2014-09-10 19:51:11EvensFsetmessageid: <>
2014-09-10 19:51:11EvensFlinkissue21228 messages
2014-09-10 19:51:11EvensFcreate