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 Nick Barnes
Recipients Nick Barnes
Date 2008-11-25.11:11:54
SpamBayes Score 1.56033e-08
Marked as misclassified No
Message-id <1227611516.22.0.455645816232.issue4426@psf.upfronthosting.co.za>
In-reply-to
Content
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.

Looking at the source of unicodeobject.c, the call to the SPECIAL macro
on line 1009 has hardcoded second and third arguments of zero.  Maybe
changing the second argument to 1 would fix this.  Maybe.
History
Date User Action Args
2008-11-25 11:11:56Nick Barnessetrecipients: + Nick Barnes
2008-11-25 11:11:56Nick Barnessetmessageid: <1227611516.22.0.455645816232.issue4426@psf.upfronthosting.co.za>
2008-11-25 11:11:55Nick Barneslinkissue4426 messages
2008-11-25 11:11:55Nick Barnescreate