2019-05-17 11:55:34 +02:00
|
|
|
.. highlight:: c
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
.. _floatobjects:
|
|
|
|
|
|
2024-07-19 11:06:02 +03:00
|
|
|
Floating-Point Objects
|
2023-06-14 19:51:30 +05:30
|
|
|
======================
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2024-07-19 11:06:02 +03:00
|
|
|
.. index:: pair: object; floating-point
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:type:: PyFloatObject
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2024-07-19 11:06:02 +03:00
|
|
|
This subtype of :c:type:`PyObject` represents a Python floating-point object.
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:var:: PyTypeObject PyFloat_Type
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2024-07-19 11:06:02 +03:00
|
|
|
This instance of :c:type:`PyTypeObject` represents the Python floating-point
|
2010-10-17 10:59:41 +00:00
|
|
|
type. This is the same object as :class:`float` in the Python layer.
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:function:: int PyFloat_Check(PyObject *p)
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
Return true if its argument is a :c:type:`PyFloatObject` or a subtype of
|
2021-01-06 12:38:26 +01:00
|
|
|
:c:type:`PyFloatObject`. This function always succeeds.
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:function:: int PyFloat_CheckExact(PyObject *p)
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
Return true if its argument is a :c:type:`PyFloatObject`, but not a subtype of
|
2021-01-06 12:38:26 +01:00
|
|
|
:c:type:`PyFloatObject`. This function always succeeds.
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:function:: PyObject* PyFloat_FromString(PyObject *str)
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
Create a :c:type:`PyFloatObject` object based on the string value in *str*, or
|
2019-10-30 12:03:20 +02:00
|
|
|
``NULL`` on failure.
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:function:: PyObject* PyFloat_FromDouble(double v)
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2019-10-30 12:03:20 +02:00
|
|
|
Create a :c:type:`PyFloatObject` object from *v*, or ``NULL`` on failure.
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:function:: double PyFloat_AsDouble(PyObject *pyfloat)
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2022-10-05 19:01:14 +01:00
|
|
|
Return a C :c:expr:`double` representation of the contents of *pyfloat*. If
|
2024-07-19 11:06:02 +03:00
|
|
|
*pyfloat* is not a Python floating-point object but has a :meth:`~object.__float__`
|
2008-01-20 09:30:57 +00:00
|
|
|
method, this method will first be called to convert *pyfloat* into a float.
|
2023-06-30 23:27:09 +09:00
|
|
|
If :meth:`!__float__` is not defined then it falls back to :meth:`~object.__index__`.
|
2011-12-18 01:25:27 +01:00
|
|
|
This method returns ``-1.0`` upon failure, so one should call
|
|
|
|
|
:c:func:`PyErr_Occurred` to check for errors.
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2019-06-02 00:05:48 +03:00
|
|
|
.. versionchanged:: 3.8
|
2023-06-30 23:27:09 +09:00
|
|
|
Use :meth:`~object.__index__` if available.
|
2019-06-02 00:05:48 +03:00
|
|
|
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:function:: double PyFloat_AS_DOUBLE(PyObject *pyfloat)
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2022-10-05 19:01:14 +01:00
|
|
|
Return a C :c:expr:`double` representation of the contents of *pyfloat*, but
|
2008-01-20 09:30:57 +00:00
|
|
|
without error checking.
|
|
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:function:: PyObject* PyFloat_GetInfo(void)
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
Return a structseq instance which contains information about the
|
|
|
|
|
precision, minimum and maximum values of a float. It's a thin wrapper
|
|
|
|
|
around the header file :file:`float.h`.
|
|
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:function:: double PyFloat_GetMax()
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2022-10-05 19:01:14 +01:00
|
|
|
Return the maximum representable finite float *DBL_MAX* as C :c:expr:`double`.
|
2008-01-20 09:30:57 +00:00
|
|
|
|
|
|
|
|
|
2010-10-06 10:11:56 +00:00
|
|
|
.. c:function:: double PyFloat_GetMin()
|
2008-01-20 09:30:57 +00:00
|
|
|
|
2022-10-05 19:01:14 +01:00
|
|
|
Return the minimum normalized positive float *DBL_MIN* as C :c:expr:`double`.
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
|
2025-11-11 13:13:59 +03:00
|
|
|
.. c:macro:: Py_INFINITY
|
|
|
|
|
|
|
|
|
|
This macro expands a to constant expression of type :c:expr:`double`, that
|
|
|
|
|
represents the positive infinity.
|
|
|
|
|
|
2025-11-12 15:44:49 +03:00
|
|
|
It is equivalent to the :c:macro:`!INFINITY` macro from the C11 standard
|
|
|
|
|
``<math.h>`` header.
|
|
|
|
|
|
|
|
|
|
.. deprecated:: 3.15
|
2025-11-18 12:17:37 +03:00
|
|
|
The macro is :term:`soft deprecated`.
|
2025-11-11 13:13:59 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
.. c:macro:: Py_NAN
|
|
|
|
|
|
|
|
|
|
This macro expands a to constant expression of type :c:expr:`double`, that
|
|
|
|
|
represents a quiet not-a-number (qNaN) value.
|
|
|
|
|
|
|
|
|
|
On most platforms, this is equivalent to the :c:macro:`!NAN` macro from
|
|
|
|
|
the C11 standard ``<math.h>`` header.
|
|
|
|
|
|
|
|
|
|
|
2025-11-18 12:17:37 +03:00
|
|
|
.. c:macro:: Py_HUGE_VAL
|
|
|
|
|
|
|
|
|
|
Equivalent to :c:macro:`!INFINITY`.
|
|
|
|
|
|
|
|
|
|
.. deprecated:: 3.14
|
|
|
|
|
The macro is :term:`soft deprecated`.
|
|
|
|
|
|
|
|
|
|
|
2025-11-12 16:37:54 +00:00
|
|
|
.. c:macro:: Py_MATH_E
|
|
|
|
|
|
|
|
|
|
The definition (accurate for a :c:expr:`double` type) of the :data:`math.e` constant.
|
|
|
|
|
|
|
|
|
|
|
2025-11-10 18:36:01 +03:00
|
|
|
.. c:macro:: Py_MATH_El
|
|
|
|
|
|
|
|
|
|
High precision (long double) definition of :data:`~math.e` constant.
|
|
|
|
|
|
|
|
|
|
.. deprecated-removed:: 3.15 3.20
|
|
|
|
|
|
|
|
|
|
|
2025-11-12 16:37:54 +00:00
|
|
|
.. c:macro:: Py_MATH_PI
|
|
|
|
|
|
|
|
|
|
The definition (accurate for a :c:expr:`double` type) of the :data:`math.pi` constant.
|
|
|
|
|
|
|
|
|
|
|
2025-11-10 18:36:01 +03:00
|
|
|
.. c:macro:: Py_MATH_PIl
|
|
|
|
|
|
|
|
|
|
High precision (long double) definition of :data:`~math.pi` constant.
|
|
|
|
|
|
|
|
|
|
.. deprecated-removed:: 3.15 3.20
|
|
|
|
|
|
|
|
|
|
|
2025-11-12 16:37:54 +00:00
|
|
|
.. c:macro:: Py_MATH_TAU
|
|
|
|
|
|
|
|
|
|
The definition (accurate for a :c:expr:`double` type) of the :data:`math.tau` constant.
|
|
|
|
|
|
|
|
|
|
.. versionadded:: 3.6
|
|
|
|
|
|
|
|
|
|
|
2025-11-05 17:00:26 -05:00
|
|
|
.. c:macro:: Py_RETURN_NAN
|
|
|
|
|
|
|
|
|
|
Return :data:`math.nan` from a function.
|
|
|
|
|
|
|
|
|
|
On most platforms, this is equivalent to ``return PyFloat_FromDouble(NAN)``.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.. c:macro:: Py_RETURN_INF(sign)
|
|
|
|
|
|
|
|
|
|
Return :data:`math.inf` or :data:`-math.inf <math.inf>` from a function,
|
|
|
|
|
depending on the sign of *sign*.
|
|
|
|
|
|
|
|
|
|
On most platforms, this is equivalent to the following::
|
|
|
|
|
|
|
|
|
|
return PyFloat_FromDouble(copysign(INFINITY, sign));
|
|
|
|
|
|
|
|
|
|
|
2025-11-18 12:17:37 +03:00
|
|
|
.. c:macro:: Py_IS_FINITE(X)
|
|
|
|
|
|
|
|
|
|
Return ``1`` if the given floating-point number *X* is finite,
|
|
|
|
|
that is, it is normal, subnormal or zero, but not infinite or NaN.
|
|
|
|
|
Return ``0`` otherwise.
|
|
|
|
|
|
|
|
|
|
.. deprecated:: 3.14
|
|
|
|
|
The macro is :term:`soft deprecated`. Use :c:macro:`!isfinite` instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.. c:macro:: Py_IS_INFINITY(X)
|
|
|
|
|
|
|
|
|
|
Return ``1`` if the given floating-point number *X* is positive or negative
|
|
|
|
|
infinity. Return ``0`` otherwise.
|
|
|
|
|
|
|
|
|
|
.. deprecated:: 3.14
|
|
|
|
|
The macro is :term:`soft deprecated`. Use :c:macro:`!isinf` instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.. c:macro:: Py_IS_NAN(X)
|
|
|
|
|
|
|
|
|
|
Return ``1`` if the given floating-point number *X* is a not-a-number (NaN)
|
|
|
|
|
value. Return ``0`` otherwise.
|
|
|
|
|
|
|
|
|
|
.. deprecated:: 3.14
|
|
|
|
|
The macro is :term:`soft deprecated`. Use :c:macro:`!isnan` instead.
|
|
|
|
|
|
|
|
|
|
|
2022-03-12 00:10:02 +01:00
|
|
|
Pack and Unpack functions
|
2023-06-14 19:51:30 +05:30
|
|
|
-------------------------
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
The pack and unpack functions provide an efficient platform-independent way to
|
|
|
|
|
store floating-point values as byte strings. The Pack routines produce a bytes
|
2022-10-05 19:01:14 +01:00
|
|
|
string from a C :c:expr:`double`, and the Unpack routines produce a C
|
|
|
|
|
:c:expr:`double` from such a bytes string. The suffix (2, 4 or 8) specifies the
|
2022-03-12 00:10:02 +01:00
|
|
|
number of bytes in the bytes string.
|
|
|
|
|
|
|
|
|
|
On platforms that appear to use IEEE 754 formats these functions work by
|
|
|
|
|
copying bits. On other platforms, the 2-byte format is identical to the IEEE
|
|
|
|
|
754 binary16 half-precision format, the 4-byte format (32-bit) is identical to
|
|
|
|
|
the IEEE 754 binary32 single precision format, and the 8-byte format to the
|
|
|
|
|
IEEE 754 binary64 double precision format, although the packing of INFs and
|
|
|
|
|
NaNs (if such things exist on the platform) isn't handled correctly, and
|
|
|
|
|
attempting to unpack a bytes string containing an IEEE INF or NaN will raise an
|
|
|
|
|
exception.
|
|
|
|
|
|
2025-11-07 21:34:49 +08:00
|
|
|
Note that NaNs type may not be preserved on IEEE platforms (signaling NaN become
|
|
|
|
|
quiet NaN), for example on x86 systems in 32-bit mode.
|
2025-05-01 17:20:36 +03:00
|
|
|
|
2022-03-12 00:10:02 +01:00
|
|
|
On non-IEEE platforms with more precision, or larger dynamic range, than IEEE
|
|
|
|
|
754 supports, not all values can be packed; on non-IEEE platforms with less
|
|
|
|
|
precision, or smaller dynamic range, not all values can be unpacked. What
|
|
|
|
|
happens in such cases is partly accidental (alas).
|
|
|
|
|
|
|
|
|
|
.. versionadded:: 3.11
|
|
|
|
|
|
|
|
|
|
Pack functions
|
2023-06-14 19:51:30 +05:30
|
|
|
^^^^^^^^^^^^^^
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
The pack routines write 2, 4 or 8 bytes, starting at *p*. *le* is an
|
2022-10-05 19:01:14 +01:00
|
|
|
:c:expr:`int` argument, non-zero if you want the bytes string in little-endian
|
2022-03-12 00:10:02 +01:00
|
|
|
format (exponent last, at ``p+1``, ``p+3``, or ``p+6`` ``p+7``), zero if you
|
2023-07-21 10:52:07 +03:00
|
|
|
want big-endian format (exponent first, at *p*). The :c:macro:`PY_BIG_ENDIAN`
|
2022-03-14 16:51:51 +01:00
|
|
|
constant can be used to use the native endian: it is equal to ``1`` on big
|
|
|
|
|
endian processor, or ``0`` on little endian processor.
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
Return value: ``0`` if all is OK, ``-1`` if error (and an exception is set,
|
|
|
|
|
most likely :exc:`OverflowError`).
|
|
|
|
|
|
|
|
|
|
There are two problems on non-IEEE platforms:
|
|
|
|
|
|
|
|
|
|
* What this does is undefined if *x* is a NaN or infinity.
|
|
|
|
|
* ``-0.0`` and ``+0.0`` produce the same bytes string.
|
|
|
|
|
|
2025-07-15 08:30:12 +03:00
|
|
|
.. c:function:: int PyFloat_Pack2(double x, char *p, int le)
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
Pack a C double as the IEEE 754 binary16 half-precision format.
|
|
|
|
|
|
2025-07-15 08:30:12 +03:00
|
|
|
.. c:function:: int PyFloat_Pack4(double x, char *p, int le)
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
Pack a C double as the IEEE 754 binary32 single precision format.
|
|
|
|
|
|
2025-07-15 08:30:12 +03:00
|
|
|
.. c:function:: int PyFloat_Pack8(double x, char *p, int le)
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
Pack a C double as the IEEE 754 binary64 double precision format.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unpack functions
|
2023-06-14 19:51:30 +05:30
|
|
|
^^^^^^^^^^^^^^^^
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
The unpack routines read 2, 4 or 8 bytes, starting at *p*. *le* is an
|
2022-10-05 19:01:14 +01:00
|
|
|
:c:expr:`int` argument, non-zero if the bytes string is in little-endian format
|
2022-03-12 00:10:02 +01:00
|
|
|
(exponent last, at ``p+1``, ``p+3`` or ``p+6`` and ``p+7``), zero if big-endian
|
2023-07-21 10:52:07 +03:00
|
|
|
(exponent first, at *p*). The :c:macro:`PY_BIG_ENDIAN` constant can be used to
|
2022-03-14 16:51:51 +01:00
|
|
|
use the native endian: it is equal to ``1`` on big endian processor, or ``0``
|
|
|
|
|
on little endian processor.
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
Return value: The unpacked double. On error, this is ``-1.0`` and
|
|
|
|
|
:c:func:`PyErr_Occurred` is true (and an exception is set, most likely
|
|
|
|
|
:exc:`OverflowError`).
|
|
|
|
|
|
|
|
|
|
Note that on a non-IEEE platform this will refuse to unpack a bytes string that
|
|
|
|
|
represents a NaN or infinity.
|
|
|
|
|
|
2025-07-15 08:30:12 +03:00
|
|
|
.. c:function:: double PyFloat_Unpack2(const char *p, int le)
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
Unpack the IEEE 754 binary16 half-precision format as a C double.
|
|
|
|
|
|
2025-07-15 08:30:12 +03:00
|
|
|
.. c:function:: double PyFloat_Unpack4(const char *p, int le)
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
Unpack the IEEE 754 binary32 single precision format as a C double.
|
|
|
|
|
|
2025-07-15 08:30:12 +03:00
|
|
|
.. c:function:: double PyFloat_Unpack8(const char *p, int le)
|
2022-03-12 00:10:02 +01:00
|
|
|
|
|
|
|
|
Unpack the IEEE 754 binary64 double precision format as a C double.
|