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 terry.reedy
Recipients BreamoreBoy, ezio.melotti, josephoenix, orsenthil, r.david.murray, terry.reedy
Date 2013-03-20.11:15:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1363778131.81.0.0333879459927.issue2052@psf.upfronthosting.co.za>
In-reply-to
Content
After thinking about it more, the real problem is that the charset setting must match the chars used and how they re encoded, so no one setting is right for all uses. An alternative to changing the default in existing versions is to at least document what it is and explain how to work around it with .replace -- for instance output.replace('ISO-8859-1', 'utf-8'). I agree that adding a parameter (charset=xxx) is a new feature.
History
Date User Action Args
2013-03-20 11:15:31terry.reedysetrecipients: + terry.reedy, orsenthil, josephoenix, ezio.melotti, r.david.murray, BreamoreBoy
2013-03-20 11:15:31terry.reedysetmessageid: <1363778131.81.0.0333879459927.issue2052@psf.upfronthosting.co.za>
2013-03-20 11:15:31terry.reedylinkissue2052 messages
2013-03-20 11:15:31terry.reedycreate