Message175304
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 (http://pypi.python.org/pypi/desktop) 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:28 | mu_mind | set | recipients:
+ mu_mind, loewis, ping, rhettinger, cben, eric.araujo, r.david.murray, ness, taschini |
2012-11-11 00:18:28 | mu_mind | set | messageid: <1352593108.58.0.816174091663.issue1065986@psf.upfronthosting.co.za> |
2012-11-11 00:18:28 | mu_mind | link | issue1065986 messages |
2012-11-11 00:18:28 | mu_mind | create | |
|