Message178617
Another option is to decide that this issue will *not* be fixed in Python 2, and Python 3 *is* the good solution if you have this issue.
Doing the work twice can cause new problems, formatting an argument twice may return two different values :-( It may have an impact on performances and may introduce regressions.
Oh by the way, it's trivial to workaround this issue in Python 2: just use a Unicode format string. For example, replace '{0}'.format(u'\u3042') with u'{0}'.format(u'\u3042').
I hate implicit conversion from bytes to Unicode in Python 2, it's maybe better to not add a new special case? |
|
Date |
User |
Action |
Args |
2012-12-30 21:49:10 | vstinner | set | recipients:
+ vstinner, doerwalter, eric.smith, ezio.melotti, pablomouzo, flox, chris.jerdonek, gkcn, s0undt3ch |
2012-12-30 21:49:10 | vstinner | set | messageid: <1356904150.66.0.113743342362.issue7300@psf.upfronthosting.co.za> |
2012-12-30 21:49:10 | vstinner | link | issue7300 messages |
2012-12-30 21:49:10 | vstinner | create | |
|