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 r.david.murray
Recipients lukasz.langa, r.david.murray, rhettinger, the_isz
Date 2011-03-18.18:09:11
SpamBayes Score 0.0010444372
Marked as misclassified No
Message-id <1300471751.88.0.23853220491.issue11597@psf.upfronthosting.co.za>
In-reply-to
Content
Well, python3 is probably pushing some people to try to add better unicode support to their python2 versions.  I think it is more a question of "is this an easy fix?" or would it require extensive changes to support unicode properly.  If it is easy (ie: it is really just a bug in configparser's string handling) I don't see a downside to fixing it.
History
Date User Action Args
2011-03-18 18:09:11r.david.murraysetrecipients: + r.david.murray, rhettinger, lukasz.langa, the_isz
2011-03-18 18:09:11r.david.murraysetmessageid: <1300471751.88.0.23853220491.issue11597@psf.upfronthosting.co.za>
2011-03-18 18:09:11r.david.murraylinkissue11597 messages
2011-03-18 18:09:11r.david.murraycreate