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 sdaoden
Recipients r.david.murray, sdaoden
Date 2011-03-25.14:23:12
SpamBayes Score 1.1200316e-07
Marked as misclassified No
Message-id <20110325141958.GA88694@sherwood.local>
In-reply-to <1301061106.04.0.568905610677.issue11584@psf.upfronthosting.co.za>
Content
On Fri, Mar 25, 2011 at 01:51:46PM +0000, R. David Murray wrote:
> I now think it is incorrect that an 8bit header causes getitem 
> to return a Header object.
> I think instead it should be returning the stringified version 
> of the header, including the unknown-8bit encoding.

It seems to be much better to either return only strings or only 
objects. 
You've prominently documented that (in a model generated from 
bytes) objects are returned, and *DesignThoughts* states that 
*all* headers will be represented as objects in the upcoming 
package, so it's my guess that many people who are currently 
programming email things using Py3K go for Header. 

Thus, to give you a neat NONONO - why not simply allowing header 
objects for decode_header(), too?
:)
History
Date User Action Args
2011-03-25 14:23:14sdaodensetrecipients: + sdaoden, r.david.murray
2011-03-25 14:23:13sdaodenlinkissue11584 messages
2011-03-25 14:23:12sdaodencreate