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 gvanrossum
Recipients gvanrossum, ishimoto
Date 2008-04-14.18:12:22
SpamBayes Score 0.011887786
Marked as misclassified No
Message-id <1208196744.05.0.736759536469.issue2630@psf.upfronthosting.co.za>
In-reply-to
Content
I think this has potential, but it is too liberal. There are many more
characters that cannot be assumed printable, e.g. many of the Latin-1
characters in the range 0x80 through 0x9F.  Isn't there some Unicode
data table that shows code points that are safely printable?

OTOH there are other potential use cases where it would be nice to see
the \u escapes, e.g. when one is concerned about sequences that print
the same but don't have the same content (e.g. pre-normalization).

The backslashreplace trick is nice, I didn't even know about that. :-)
History
Date User Action Args
2008-04-14 18:12:26gvanrossumsetspambayes_score: 0.0118878 -> 0.011887786
recipients: + gvanrossum, ishimoto
2008-04-14 18:12:24gvanrossumsetspambayes_score: 0.0118878 -> 0.0118878
messageid: <1208196744.05.0.736759536469.issue2630@psf.upfronthosting.co.za>
2008-04-14 18:12:23gvanrossumlinkissue2630 messages
2008-04-14 18:12:22gvanrossumcreate