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 lemburg
Recipients belopolsky, docs@python, ezio.melotti, georg.brandl, lemburg, loewis, vstinner
Date 2011-04-15.17:23:35
SpamBayes Score 4.440892e-16
Marked as misclassified No
Message-id <4DA87F0D.1050800@egenix.com>
In-reply-to <1302887747.85.0.115725716249.issue10665@psf.upfronthosting.co.za>
Content
Ezio Melotti wrote:
> 
> Ezio Melotti <ezio.melotti@gmail.com> added the comment:
> 
> One reason is that unicodedata.lookup actually returns a unicode char, so if we want to show a code snippet that uses unicodedata.lookup we either have to use a unicode literal or limit the chars in the examples to latin1 to make sure it works nice with the PDF generator.

Why not wrap the calls with a repr() ?

> Using escape sequences elsewhere might work, but in some examples it's better to use the actual chars IMHO (except that they don't work with the PDF).

Sure, it'll look nicer, but it will also make comparing the examples
with the actual output users see on the screen error-prone (e.g. if
the fonts don't have the necessary glyphs).

Copy&paste will also often fail.

I think it's more useful to show examples that more or less always
work, than ones which display all available goodies.
History
Date User Action Args
2011-04-15 17:23:36lemburgsetrecipients: + lemburg, loewis, georg.brandl, belopolsky, vstinner, ezio.melotti, docs@python
2011-04-15 17:23:35lemburglinkissue10665 messages
2011-04-15 17:23:35lemburgcreate