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 serhiy.storchaka
Recipients eric.smith, facundobatista, mark.dickinson, rhettinger, serhiy.storchaka
Date 2021-11-28.20:30:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638131452.38.0.983600077255.issue45739@roundup.psfhosted.org>
In-reply-to
Content
I have no strong opinion. I found the discrepancy when reviewed one of Mark's PRs. I was surprised because I did not know that "N" is supported.

On other hand, there are reasons for supporting upper-case variant of "n" if we support upper-case variants of "e", "g" and "x" (formats which produce output containing letters).

There is an alternative solution of the problem solved by upper-case variations of formats: add a special converter for converting a string to upper case, so for example f'{x:12.8E}' could be written as f'{x:12.8e!u}'.

I prefer -1 or 2. If we choose deprecation I prefer adding an upper-case converter.
History
Date User Action Args
2021-11-28 20:30:52serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, facundobatista, mark.dickinson, eric.smith
2021-11-28 20:30:52serhiy.storchakasetmessageid: <1638131452.38.0.983600077255.issue45739@roundup.psfhosted.org>
2021-11-28 20:30:52serhiy.storchakalinkissue45739 messages
2021-11-28 20:30:52serhiy.storchakacreate