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 eric.smith
Recipients John Belmonte, eric.smith, mark.dickinson, serhiy.storchaka, steven.daprano
Date 2021-12-07.21:48:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638913696.88.0.201725595785.issue45995@roundup.psfhosted.org>
In-reply-to
Content
PyOS_double_to_string is part of the stable ABI. I don't recall if we're allowed to add new bitfield flags to a stable ABI function. We'd use a new Py_DTSF_NORMALIZE_NEGATIVE_0 flag for this feature.

I suspect we can't add a flag, due to comparability reasons (new code setting the flag being used in old versions of python without it), but we'd need to research. I saw a similar discussion within the last few years, but of course now I can't find it. Maybe old versions would correctly ignore the new bit being set.

This proposal becomes less interesting if we'd need to add a new function to support it. Although I guess we could do something that's internal-only.
History
Date User Action Args
2021-12-07 21:48:17eric.smithsetrecipients: + eric.smith, mark.dickinson, steven.daprano, serhiy.storchaka, John Belmonte
2021-12-07 21:48:16eric.smithsetmessageid: <1638913696.88.0.201725595785.issue45995@roundup.psfhosted.org>
2021-12-07 21:48:16eric.smithlinkissue45995 messages
2021-12-07 21:48:16eric.smithcreate