[issue22989] HTTPResponse.msg not as documented

Martin Panter added the comment: The documentation now mentions the “msg” quirk and the info() method. -- resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.5, Python 3.6 ___ Python tracker

[issue22989] HTTPResponse.msg not as documented

Roundup Robot added the comment: New changeset fa3c9faabfb0 by Martin Panter in branch '3.4': Issues #22989, #21228: Document HTTP response object for urlopen() https://hg.python.org/cpython/rev/fa3c9faabfb0 New changeset b55c006b79bc by Martin Panter in branch '3.5': Issue #22989, #21228: Merge

[issue22989] HTTPResponse.msg not as documented

Martin Panter added the comment: Documenting the “headers” attribute is also discussed in Issue 12707 -- ___ Python tracker ___ ___ Py

[issue22989] HTTPResponse.msg not as documented

Martin Panter added the comment: See Issue 21228 for a patch which documents the “.msg” hack, and that the info() method is available for HTTP responses. I think documenting the “.headers” attribute would be a bad idea, because it is introducing yet another way to do what the almost-documented

[issue22989] HTTPResponse.msg not as documented

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue22989] HTTPResponse.msg not as documented

New submission from Paul Hartmann: HTTPResponse.msg is documented as a http.client.HTTPMessage object containing the headers of the response [1]. But in fact this is a string containing the status code: >>> import urllib.request >>> req=urllib.request.urlopen('http://heise.de') >>> content = r