[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Joel Verhagen added the comment: There is a difference in what HTTPResponse.getheaders() returns. Python 2.7.2 (default, Jun 12 2011, 14:24:46) [MSC v.1500 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import httplib >>> c = httplib.HTTPCon

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Changes by Petri Lehtinen : -- nosy: +petri.lehtinen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Changes by Sridhar Ratnakumar : -- nosy: +srid ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Senthil added the comment: I spent sometime on the patch which replaces the self.msg usage with self.headers in http.client. Everything is fine. The next step is to provide an interface in the urllib.response and the equivalent changes to py2k. -- assignee: georg.brandl -> jhylton resol

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Jeremy Hylton added the comment: The attached file is vaguely related to the current discussion. I'd like to document the API for the urllib response, but I'd also like to simplify the implementation on the py3k side. We can document the simple API on the py3k side, then support some version o

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Brad Miller added the comment: On Thu, Mar 26, 2009 at 4:29 PM, Barry A. Warsaw wrote: > > Barry A. Warsaw added the comment: > > I propose that you only document the getitem header access API. I.e. > the thing that info() gives you can be used to access the message > headers via message['con

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Barry A. Warsaw added the comment: I propose that you only document the getitem header access API. I.e. the thing that info() gives you can be used to access the message headers via message['content-type']. That's an API common to both rfc822.Messages (the ultimate base class of mimetools.Mess

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Jeremy Hylton added the comment: A plausible solution is to pick some core set of functionality that we think people need and document that API. We can modify one or both of the current implementations to include that functionality. What do we need? -- ___

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Jeremy Hylton added the comment: No deep thought was given to the HTTPMessage API. Here's the extent of the discussion that I can find. I've changed the names, but you can find the full discussion at http://bugs.python.org/issue2848 A: mimetools.Message is compatible with email.message.Messag

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Changes by Brad Miller : -- nosy: +bmiller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Changes by Daniel Diniz : -- nosy: +jjlee ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Changes by Daniel Diniz : -- dependencies: +httplib.HTTPMessage undocumented ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Daniel Diniz added the comment: ISTM that these issues tend to go all the way up to test coverage and organization :/ -- assignee: -> georg.brandl components: +Documentation nosy: +ajaksu2, georg.brandl, orsenthil stage: -> test needed ___ Python t

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

David M. Beazley added the comment: Verified that 2to3 does not fix this. ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

New submission from David M. Beazley : A file-like object u returned by the urlopen() function in both Python 2.6/3.0 has a method info() that returns a 'HTTPMessage' object. For example: ::: Python 2.6 >>> from urllib2 import urlopen >>> u = urlopen("http://www.python.org";) >>> u.info() >>