+--------+--------------------------+--------------------+----------------+------------+
| ``d`` | :c:expr:`double` | float | 8 | \(4) |
+--------+--------------------------+--------------------+----------------+------------+
-| ``F`` | :c:expr:`float complex` | complex | 8 | \(10) |
-+--------+--------------------------+--------------------+----------------+------------+
-| ``D`` | :c:expr:`double complex` | complex | 16 | \(10) |
-+--------+--------------------------+--------------------+----------------+------------+
| ``Zf`` | :c:expr:`float complex` | complex | 8 | \(10) |
+--------+--------------------------+--------------------+----------------+------------+
| ``Zd`` | :c:expr:`double complex` | complex | 16 | \(10) |
.. versionchanged:: 3.15
Added support for the ``'Zf'`` and ``'Zd'`` formats.
+ ``'F'`` and ``'D'`` formats are :term:`soft deprecated`.
.. seealso::
are accepted.
(10)
- For the ``'F'`` and ``'D'`` format characters, the packed representation uses
+ For the ``'Zf'`` and ``'Zd'`` type codes, the packed representation uses
the IEEE 754 binary32 and binary64 format for components of the complex
number, regardless of the floating-point format used by the platform.
- Note that complex types (``F``/``Zf`` and ``D``/``Zd``) are available unconditionally,
+ Note that complex types are available unconditionally,
despite complex types being an optional feature in C.
As specified in the C11 standard, each complex type is represented by a
two-element C array containing, respectively, the real and imaginary parts.
+ The ``'F'`` and ``'D'`` (for ``'Zf'`` and ``'Zd'``, respectively) format
+ characters are supported for compatibility.
A format character may be preceded by an integral repeat count. For example,
(Contributed by Sergey B Kirpichev and Serhiy Storchaka in :gh:`143715`.)
+ * Using ``'F'`` and ``'D'`` type codes now are :term:`soft deprecated`
+ in favor of two-letter forms ``'Zf'`` and ``'Zd'``.
+ (Contributed by Sergey B Kirpichev in :gh:`121249`.)
+
+
* :mod:`typing`:
* The following statements now cause ``DeprecationWarning``\ s to be emitted