Author skrah
Recipients eric.smith, mark.dickinson, serhiy.storchaka, skrah, steelman, vstinner
Date 2019-01-09.10:09:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1547028563.67.0.985967187906.issue35638@roundup.psfhosted.org>
In-reply-to
Content
> Since it seems like we are still at the "idea" stage, would it make sense to add a function which accept options to choose how to format a number?

Maybe, but I think for format() Eric's latest proposal on python-ideas is great ("*f" for "f + LC_NUMERIC", "$f" for "f + LC_MONETARY".

For me that's sufficient. Does locale.format_string() handle the other cases?


> By the way, the decimal module doesn't support properly the following corner case: LC_NUMERIC using an encoding different than LC_CTYPE encoding. I wrote https://github.com/python/cpython/pull/5191 but I abandonned my change.

Well, I *discovered and opened* #7442 several years ago, and you said:

"I see that various people contributed to the issue, but it looks like the only user asking for the request is Stefan Krah. I prefer to close the issue and wait until more users ask for it before considering again the patch, or find a different way to implement the feature (support LC_NUMERIC and LC_CTYPE locales using a different encoding)."


So why would you think that I'm not aware of that issue? It has low priority for me and I hesitate to depend on the official locale functions in decimal because I don't want to be involved in additional issue reports in that area.
History
Date User Action Args
2019-01-09 10:09:24skrahsetrecipients: + skrah, mark.dickinson, vstinner, eric.smith, serhiy.storchaka, steelman
2019-01-09 10:09:23skrahsetmessageid: <1547028563.67.0.985967187906.issue35638@roundup.psfhosted.org>
2019-01-09 10:09:23skrahlinkissue35638 messages
2019-01-09 10:09:23skrahcreate