[issue4773] HTTPMessage not documented and has inconsistent API across Py2/Py3

[Socob]

Changes by Socob <206a8...@opayq.com>:


--
nosy: +Socob

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4773] HTTPMessage not documented and has inconsistent API across Py2/Py3

[Berker Peksag]

Changes by Berker Peksag :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4773] HTTPMessage not documented and has inconsistent API across Py2/Py3

[Martin Panter]

Martin Panter added the comment:

Jeremy’s patch appears to have been merged in revision 9eceb618274a. A 
documentation entry for the HTTPMessage class was also added in 2009, pointing 
back to email.message.Message. So is there anything left to do for this issue?

--
nosy: +vadmium

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4773] HTTPMessage not documented and has inconsistent API across Py2/Py3

[Hugo Lopes Tavares]

Hugo Lopes Tavares added the comment:

I just caught a bug because on Python 3 `HTTPMessage` has `get_param`, while on 
Python 2 there is `getparam`, with a different method signature. I am trying to 
figure out a solution so my code can run in both python 2 and 3 without ifs on 
python version.

--
nosy: +hltbra

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4773] HTTPMessage not documented and has inconsistent API across Py2/Py3

[Piotr Dobrogost]

Piotr Dobrogost added the comment:

...continuing my previous comment

Joining headers with the same name by ", " by HTTPResponse.getheaders() in 
Python 2.7 is wrong and there's a bug for this - see 
http://bugs.python.org/issue1660009

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4773] HTTPMessage not documented and has inconsistent API across Py2/Py3

[Piotr Dobrogost]

Piotr Dobrogost added the comment:

@joel.verhagen

"Should HTTPResponse.getheaders() comma-separate the values (...)"

No, it should not. RFC 2616 states:

"Multiple message-header fields with the same field-name MAY be present in a 
message if and only if the entire field-value for that header field is defined 
as a comma-separated list [i.e., #(values)]."

As field-values for some header fields ('Set-Cookie' being an example) are not 
defined as a comma-separated list such fields must not be merged.

Side note:
RFC 2616 is very soon to be obsoleted by the new RFC from httpbin working 
group. However, in the current/newest draft 
(http://trac.tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-21#section-3.2)
 although wording is different the sense is the same.

--
nosy: +piotr.dobrogost

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4773] HTTPMessage not documented and has inconsistent API across Py2/Py3

[Ezio Melotti]

Ezio Melotti  added the comment:

Yep, #12707.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4773] HTTPMessage not documented and has inconsistent API across Py2/Py3

[Éric Araujo]

Changes by Éric Araujo :


Removed file: http://bugs.python.org/file13430/unnamed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4773] HTTPMessage not documented and has inconsistent API across Py2/Py3

[Éric Araujo]

Éric Araujo  added the comment:

Now that two Python 3 releases have been made, I don’t know if changing the 
code is still an option.  The doc can certainly still be improved.

Adding Ezio to nosy; I think it’s you who opened a bug report about removing 
superfluous getter methods in the addinfourl class (and other ugliness).

--
nosy: +ezio.melotti
resolution: accepted -> 
stage: test needed -> patch review
title: HTTPMessage not documented and has inconsistent API across 2.6/3.0 -> 
HTTPMessage not documented and has inconsistent API across Py2/Py3
versions: +Python 2.7, Python 3.2, Python 3.3 -Python 2.6, Python 3.0

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com