R. David Murray <rdmur...@bitdance.com> added the comment: Discussion of the new API, and what changes will be made for 3.3, will take place on the email-sig mailing list (see http://mail.python.org). Please join! Right now it is a dormant list, but I plan to post some stuff soon :)
The more I stare at the set_charset code and try to write out the actual algorithm in words, the buggier this looks. If the input and output charsets differ, the body encoding is done unconditionally, but the CTE is set in that case only if the CTE header doesn't exist. I've attached a proposed doc patch which tries to describe the actual algorithm. If you'd care to take a look and see if you see any mistakes in my description, that would be great. Note that you have to go down a couple of twisty passages if you want to fully understand what the set_charset code is doing. ---------- components: +Documentation keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file20829/set_charset_doc.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11216> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
