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 lambacck
Recipients belopolsky, catherine, doerwalter, eric.araujo, ezio.melotti, georg.brandl, gpolo, lambacck, orsenthil, r.david.murray, rhettinger, ron_adam, vstinner
Date 2011-08-07.01:40:11
SpamBayes Score 2.0455773e-09
Marked as misclassified No
Message-id <1312681212.2.0.965698460587.issue10087@psf.upfronthosting.co.za>
In-reply-to
Content
Senthil: I think that would fundamentally make things worse. The HTML calendar apparently always provides a bytes type, but lets assume it provided you with unicode and we used sys.stdout.write on the output. Fundamentally you would get the same behavior as the patch provides since if you don't provide an encoding it uses sys.getdefaultencoding() which, IIUC is fundamentally what happens if you sys.stdout.write a unicode string.

Ezio: I think it is highly unlikely that someone would be fiddling around with sys.stdout and then calling the main() function on calendar.main() (after setting up sys.args so that option parser gets the right parameters).
History
Date User Action Args
2011-08-07 01:40:12lambaccksetrecipients: + lambacck, doerwalter, georg.brandl, rhettinger, belopolsky, orsenthil, vstinner, ron_adam, gpolo, ezio.melotti, eric.araujo, r.david.murray, catherine
2011-08-07 01:40:12lambaccksetmessageid: <1312681212.2.0.965698460587.issue10087@psf.upfronthosting.co.za>
2011-08-07 01:40:11lambaccklinkissue10087 messages
2011-08-07 01:40:11lambacckcreate