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 rhettinger
Recipients dabeaz, mark.dickinson, r.david.murray, rhettinger
Date 2010-12-28.00:13:59
SpamBayes Score 0.0002807859
Marked as misclassified No
Message-id <1293495243.64.0.30838622421.issue10783@psf.upfronthosting.co.za>
In-reply-to
Content
A possible answer to "why is this encoding at all" was probably to make it easier to transition code from python 2.x where strings were usually ascii and it would make no difference in output if encoded in utf-8.  The 2-to-3 fixer was good at handling name changes but not bytes/text issues.  That is just a guess at what the developer may have been thinking.
History
Date User Action Args
2010-12-28 00:14:03rhettingersetrecipients: + rhettinger, mark.dickinson, r.david.murray, dabeaz
2010-12-28 00:14:03rhettingersetmessageid: <1293495243.64.0.30838622421.issue10783@psf.upfronthosting.co.za>
2010-12-28 00:13:59rhettingerlinkissue10783 messages
2010-12-28 00:13:59rhettingercreate