Issue #5211: Fix complex type to avoid implicit calls to
complex.__coerce__. Thanks Meador Inge for the patch.
diff --git a/Doc/reference/datamodel.rst b/Doc/reference/datamodel.rst
index 0dc4187..2542704 100644
--- a/Doc/reference/datamodel.rst
+++ b/Doc/reference/datamodel.rst
@@ -2271,13 +2271,15 @@
*
In the current implementation, the built-in numeric types :class:`int`,
- :class:`long` and :class:`float` do not use coercion; the type :class:`complex`
- however does use coercion for binary operators and rich comparisons, despite
- the above rules. The difference can become apparent when subclassing these
- types. Over time, the type :class:`complex` may be fixed to avoid coercion.
+ :class:`long`, :class:`float`, and :class:`complex` do not use coercion.
All these types implement a :meth:`__coerce__` method, for use by the built-in
:func:`coerce` function.
+ .. versionchanged:: 2.7
+
+ The complex type no longer makes implicit calls to the :meth:`__coerce__`
+ method for mixed-type binary arithmetic operations.
+
.. _context-managers: