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 pitrou
Recipients BreamoreBoy, barry, pitrou, r.david.murray
Date 2010-10-04.15:24:49
SpamBayes Score 3.8602822e-05
Marked as misclassified No
Message-id <1286205884.3178.45.camel@localhost.localdomain>
In-reply-to <1286205521.06.0.950416103352.issue6302@psf.upfronthosting.co.za>
Content
> I agree that it makes sense to have consistent types in the output.
> As for whether to add a new method or fix the existing one, I'm a bit
> torn, but I'd probably opt for fixing the existing function rather
> than adding a new one, just because I think there are few Python 3
> applications out there that are counting on the old behavior.  (I
> could be wrong though ;).

The point of a new method is to return the header as a human-readable
string, rather than a list of tuples. It has added value besides leaving
the old method alone ;)
History
Date User Action Args
2010-10-04 15:24:51pitrousetrecipients: + pitrou, barry, r.david.murray, BreamoreBoy
2010-10-04 15:24:49pitroulinkissue6302 messages
2010-10-04 15:24:49pitroucreate