Antoine Pitrou <pit...@free.fr> added the comment: > 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 :) ---------- nosy: +pitrou _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1078919> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
