Message170586
| Author | chris.jerdonek |
|---|---|
| Recipients | Arfrever, Ariel.Ben-Yehuda, berker.peksag, chris.jerdonek, eric.smith, ezio.melotti, loewis, serhiy.storchaka |
| Date | 2012-09-17.06:22:06 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1347862927.66.0.700416644802.issue15276@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Eric, it looks like you wrote this comment: /* don't define FORMAT_LONG, FORMAT_FLOAT, and FORMAT_COMPLEX, since we can live with only the string versions of those. The builtin format() will convert them to unicode. */ in http://hg.python.org/cpython/file/19601d451d4c/Python/formatter_unicode.c It seems like the current issue may be a valid reason for introducing a unicode FORMAT_INT (i.e. not just for type-purity and PEP 3101 compliance, but to avoid an exception). What do you think? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-09-17 06:22:07 | chris.jerdonek | set | recipients: + chris.jerdonek, loewis, eric.smith, ezio.melotti, Arfrever, berker.peksag, serhiy.storchaka, Ariel.Ben-Yehuda |
| 2012-09-17 06:22:07 | chris.jerdonek | set | messageid: <1347862927.66.0.700416644802.issue15276@psf.upfronthosting.co.za> |
| 2012-09-17 06:22:07 | chris.jerdonek | link | issue15276 messages |
| 2012-09-17 06:22:06 | chris.jerdonek | create | |