[issue40874] Update to libmpdec-2.5.0
Stefan Krah
report at bugs.python.org
Sat Jul 4 19:44:06 EDT 2020
Stefan Krah <stefan at bytereef.org> added the comment:
> In any case, I would have had a hard time giving a competent opinion on this issue.
Essentially it's a really simple Linux packaging issue for the
external libmpdec. To have the exact same behavior for the external
libmpdec as for the included libmpdec, packagers must use:
3.8 <--> 2.4.2
3.9 <--> 2.5.0
ArchLinux had no problems. Debian, and by extension Ubuntu, requires
3.8 and 3.9 to be on the same system during a transitional period, as
pointed out in msg372928 (which is really the most important message
of this whole thread).
The commit that pinned _decimal to libmpdec version 2.5.0 broke this
use case, but there are workarounds.
My stance is that it is important that libmpdec is pinned so distros
don't use a divergent version. Since there are multiple mitigations
for Debian, I don't feel particularly guilty.
Review of the commit that pinned 2.5.0 would have led to the exact
same outcome: I would have pointed that out on GitHub.
Note that with the Debian scheme there is never a good time to
update libmpdec, regardless of the release cycle.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue40874>
_______________________________________
More information about the Python-bugs-list
mailing list