➜

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 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.
History
Date User Action Args
2010-11-20 17:38:46belopolskysetrecipients: + belopolsky, amaury.forgeotdarc, vstinner, ezio.melotti
2010-11-20 17:38:45belopolskylinkissue9769 messages
2010-11-20 17:38:44belopolskycreate