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 mu_mind
Recipients cben, eric.araujo, loewis, mu_mind, ness, ping, r.david.murray, rhettinger, taschini
Date 2012-11-11.00:18:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I just ran into this, and I'd like to communicate how unfortunate it is that it's not a priority to fix this fairly trivial (?) bug. It means there's no way to define a unicode string literal with non-ascii characters that won't crash the builtin help() command.

I ran into this with the desktop package ( where the only useful documentation right now is the source code and the docstrings. Apparently the author, who has non-ascii characters in his name, did me a favor by using broken encoding on the doc string so that at least I could read everything except for his name in the help. I tried to correct the encoding and found I get a nice traceback instead of help. And to top it all off, googling for things like "help unicode docstring" and "python help ascii codec" turns up nothing. I only found this issue once I thought to include "pipepager" in the search...
Date User Action Args
2012-11-11 00:18:28mu_mindsetrecipients: + mu_mind, loewis, ping, rhettinger, cben, eric.araujo, r.david.murray, ness, taschini
2012-11-11 00:18:28mu_mindsetmessageid: <>
2012-11-11 00:18:28mu_mindlinkissue1065986 messages
2012-11-11 00:18:28mu_mindcreate