Message178617
| Author |
vstinner |
| Recipients |
chris.jerdonek, doerwalter, eric.smith, ezio.melotti, flox, gkcn, pablomouzo, s0undt3ch, vstinner |
| Date |
2012年12月30日.21:49:10 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1356904150.66.0.113743342362.issue7300@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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? |
|