Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: On 2008-11-25 12:11, Nick Barnes wrote: > New submission from Nick Barnes <[EMAIL PROTECTED]>: > > UTF-7 decoding raises an exception for any character not in the RFC2152 > "Set D" (directly encoded characters). In particular, it raises an > exception for characters in "Set O" (optional direct characters), such > as < = > [ ] @ etc. These characters can legitimately appear in > UTF-7-encoded text, and should be decoded (as themselves). As it is, > the UTF-7 decoder can't reliably be used to decode any UTF-7 text other > than that encoded by Python's own UTF-7 encoder.
Thanks for noticing this. Apparently, the UTF-7 codec is not used a lot by Python users, since it's been like this for years. The tests we have do check round-trip safety, but not the special characteristics of the UTF-7 codec. Also note that the code for the codec was contributed and is, AFAIK, not maintained by any of the Python developers. ---------- nosy: +lemburg _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4426> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
