➜

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 belopolsky
Recipients belopolsky, doerwalter, eric.araujo, ezio.melotti, georg.brandl, gpolo, lambacck, rhettinger, vstinner
Date 2010-11-23.05:03:14
SpamBayes Score 8.226238e-06
Marked as misclassified No
Message-id <1290488596.66.0.0130358932994.issue10087@psf.upfronthosting.co.za>
In-reply-to
Content 
I wonder: do we really need "encoding" option to the calendar output?  It is really not the job of the calendar module to deal with encodings.  The calendar module should produce text calendars as unicode strings and HTML calendars as UTF-8 bytes.  If someone wants to save them in a specific encoding, there are plenty of ways to achieve that.
History
Date User Action Args
2010-11-23 05:03:16belopolskysetrecipients: + belopolsky, doerwalter, georg.brandl, rhettinger, vstinner, gpolo, ezio.melotti, eric.araujo, lambacck
2010-11-23 05:03:16belopolskysetmessageid: <1290488596.66.0.0130358932994.issue10087@psf.upfronthosting.co.za>
2010-11-23 05:03:14belopolskylinkissue10087 messages
2010-11-23 05:03:14belopolskycreate