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 John Belmonte
Recipients John Belmonte, eric.smith, jbelmonte, mark.dickinson, serhiy.storchaka, steven.daprano
Date 2021-12-12.08:31:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639297887.28.0.671126054271.issue45995@roundup.psfhosted.org>
In-reply-to
Content
> For Decimal, we'd need to "own" the string formatting, taking that responsibility away from mpdecimal, but there are already other reasons to do that.

After some digging, I believe this is the background on forking pieces of mpdecimal (and why the existing source copy inside Python doesn't count as a fork):
  https://bugs.python.org/issue45708#msg405895
  https://github.com/python/cpython/pull/29438

If I understand correctly, the PR for supporting underscore separators in Decimal formatting is only taking control of generating a mpd_spec_t from the spec string.  Formatting itself is still done by mpd_qformat_spec().

So there's outstanding work to also pull the formatting code itself into _decimal.c.  (And this is wanted anyway to reconcile existing libmpdec formatting modifications:  https://github.com/python/cpython/commit/298131a44896a4fec1ea829814ad52409d59aba5)

And this is all because vendors have the crazy practice of unbundling libmpdec from Python.  (If a project is bundling the source of another, there may be some reason...?)
History
Date User Action Args
2021-12-12 08:31:27John Belmontesetrecipients: + John Belmonte, mark.dickinson, jbelmonte, eric.smith, steven.daprano, serhiy.storchaka
2021-12-12 08:31:27John Belmontesetmessageid: <1639297887.28.0.671126054271.issue45995@roundup.psfhosted.org>
2021-12-12 08:31:27John Belmontelinkissue45995 messages
2021-12-12 08:31:27John Belmontecreate