On Tue, 01 Mar 2011 17:59:10 -0500, "R. David Murray" <rdmur...@bitdance.com> wrote: > On Tue, 01 Mar 2011 13:58:50 -0800, Glenn Linderman <v+pyt...@g.nevcal.com> > wrote: > > To support reading byte-stream HTTP headers, therefore, it is critical > > that the email API accept an encoding from the application which "knows" > > the encoding; presently cgi.py has to pre-decode incoming headers > > because email does not have such a parameter. On the other hand, maybe > > cgi.py shouldn't use email header parsing at all... since browsers don't > > use RFC 2047 encoding in practice, the parsing of headers without such > > is straightforward. > > I think it could make sense for the default input character set to be > a policy parameter for the parser. Maybe not in the first version, > though :)
Just to clarify: in the first version I check in. I'd expect to decide about that part of the API not too far in to the development process, and certainly well before 3.3. --David _______________________________________________ Email-SIG mailing list Email-SIG@python.org Your options: http://mail.python.org/mailman/options/email-sig/archive%40mail-archive.com
