➜

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 skrah
Recipients belopolsky, eric.smith, ezio.melotti, lemburg, mark.dickinson, skrah, vstinner
Date 2010-12-02.23:32:00
SpamBayes Score 1.1164292e-05
Marked as misclassified No
Message-id <20101202233159.GA26436@yoda.bytereef.org>
In-reply-to <AANLkTimx9h8SE2-DPSikyR7AJECuPmyJ1douXeRt0AqP@mail.gmail.com>
Content 
Alexander Belopolsky <report@bugs.python.org> wrote:
> On Thu, Dec 2, 2010 at 4:34 PM, Marc-Andre Lemburg
> <report@bugs.python.org> wrote:
> ..
> >  * Please change the API _PyUnicode_NormalizeDecimal() to
> >   PyUnicode_ConvertToASCIIDecimal() - that's closer to what
> >   it does.
> >
> 
> Are you sure it is a good idea to give it a public name?  I have no
> problem with calling it _PyUnicode_ConvertToASCIIDecimal().
> ("Transform" may be a better term, though.)

I like the public name. Extension authors can use it and be sure that
their programs accept exactly the same numeric strings as the rest of
Python.

Are you worried that the semantics might change? If they do, I would
actually welcome to have an official transformation function that
automatically follows the current preferences of python-dev (or the
Unicode Consortium).
History
Date User Action Args
2010-12-02 23:32:04skrahsetrecipients: + skrah, lemburg, mark.dickinson, belopolsky, vstinner, eric.smith, ezio.melotti
2010-12-02 23:32:01skrahlinkissue10557 messages
2010-12-02 23:32:00skrahcreate