Message121693
| Author |
belopolsky |
| Recipients |
amaury.forgeotdarc, belopolsky, ezio.melotti, vstinner |
| Date |
2010年11月20日.17:38:44 |
| SpamBayes Score |
8.2338454e-07 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTin_gy-Axny8BOjUtKmmutcDJ0xpqYy58CJhDH0t@mail.gmail.com> |
| In-reply-to |
<201011200115.49177.victor.stinner@haypocalc.com> |
| Content |
On Fri, Nov 19, 2010 at 7:15 PM, STINNER Victor <report@bugs.python.org> wrote:
..
>
> Why should we do that? ASCII format is just fine. Remember that
> PyUnicode_FromFormatV() is part of the C API. I don't think that anyone would
> use non-ASCII format in C.
Why not. Gettext manual is full of examples with i18nalized format strings.
> If someone does that, (s)he should open a new issue
> for that :-)
Why new issue? The title of this issue fits perfectly and IMO it is
hard to argue that to "handle non-ascii text correctly" means to raise
an error when non-ascii text is encountered. |
|