[issue46852] Remove float.__get_format__() and float.__set_format__()

STINNER Victor added the comment: I wrote GH-31558 to fix the typo in the method name. -- ___ Python tracker ___ ___

[issue46852] Remove float.__get_format__() and float.__set_format__()

Change by STINNER Victor : -- keywords: +patch pull_requests: +29680 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31558 ___ Python tracker ___

[issue46852] Remove float.__get_format__() and float.__set_format__()

STINNER Victor added the comment: Oh wait, I'm now confused by the method names. In Python 3.10, the correct names at: * float.__getformat__() <= 4 underscores * float.__set_format__() <= 5 underscores It's even more confusing because the "set format" is only used in one place: test_float,

[issue46852] Remove float.__get_format__() and float.__set_format__()

STINNER Victor added the comment: See also bpo-46656: "Remove the Py_NO_NAN macro: require NAN to build Python 3.11". -- ___ Python tracker ___

[issue46852] Remove float.__get_format__() and float.__set_format__()

Raymond Hettinger added the comment: I would not miss these methods. Unless Mark says they are needed, +1 for removal. -- nosy: +mark.dickinson, rhettinger, tim.peters ___ Python tracker

[issue46852] Remove float.__get_format__() and float.__set_format__()

New submission from STINNER Victor : It has been decided to require IEEE 754 to build Python 3.11: https://mail.python.org/archives/list/python-...@python.org/thread/J5FSP6J4EITPY5C2UJI7HSL2GQCTCUWN/ At Python startup, _PyFloat_InitState() checks the IEEE 754 format at runtime. It can be