➜

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 ajaksu2, barry, loewis, pitrou, r.david.murray, tlau
Date 2010-10-03.19:25:31
SpamBayes Score 8.276031e-07
Marked as misclassified No
Message-id <1286133934.56.0.300395995007.issue1078919@psf.upfronthosting.co.za>
In-reply-to
Content 
> In addition, in 3.2 I will disallow non-ASCII parameter values unless
> they are specified in a three element tuple as in the example above.

Why would the caller be required to choose an encoding while you could simply default to utf-8? There doesn't seem to be much value in forcing the use of e.g. iso-8859-15.
Also, I'm not sure I understand what the goal of email6 is if you're breaking compatibility in email5 anyway :)
History
Date User Action Args
2010-10-03 19:25:34pitrousetrecipients: + pitrou, loewis, barry, tlau, ajaksu2, r.david.murray
2010-10-03 19:25:34pitrousetmessageid: <1286133934.56.0.300395995007.issue1078919@psf.upfronthosting.co.za>
2010-10-03 19:25:32pitroulinkissue1078919 messages
2010-10-03 19:25:31pitroucreate