Searched refs:coercion (Results 1 – 25 of 26) sorted by relevance
12
| /external/python/cpython2/Include/ |
| D | object.h | 138 typedef int (*coercion)(PyObject **, PyObject **); typedef
245 coercion nb_coerce;
|
| /external/python/cpython2/Doc/reference/ |
| D | datamodel.rst | 2153 coercion rules would become too complicated).
2240 ask the other object to attempt a coercion (but sometimes, if the implementation
2251 This section used to document the rules for coercion. As the language has
2252 evolved, the coercion rules have become hard to document precisely; documenting
2254 here are some informal guidelines regarding coercion. In Python 3, coercion
2259 If the left operand of a % operator is a string or Unicode object, no coercion
2264 It is no longer recommended to define a coercion operation. Mixed-mode
2265 operations on types that don't define coercion pass the original arguments to
2310 When either operand type defines a coercion, this coercion is called before that
2312 the coercion returns an object of a different type for the operand whose
[all …]
|
| D | expressions.rst | 36 coercion rules listed at :ref:`coercion-rules`. If both arguments are standard
870 type. The result type is that of the arguments after coercion.
872 With mixed operand types, the coercion rules for binary arithmetic operators
874 operands (after coercion) unless the second argument is negative; in that case,
|
| /external/python/cpython2/Doc/c-api/ |
| D | typeobj.rst | 23 Typedefs: unaryfunc, binaryfunc, ternaryfunc, inquiry, coercion, intargfunc,
484 the current type as their type, and the caller is supposed to perform a coercion
1186 coercion nb_coerce; /* Used by the coerce() function */
1222 the coercion method specified by the :attr:`nb_coerce` member to convert the
1225 .. c:member:: coercion PyNumberMethods.nb_coerce
1237 defined type). This is the recommended way; with Python 3 coercion will
|
| D | unicode.rst | 368 throughout the interpreter whenever coercion to Unicode is needed.
|
| /external/python/cpython2/Doc/ |
| D | glossary.rst | 111 coercion
120 ``operator.add(3.0, 4.5)``. Without coercion, all arguments of even
371 coerced (see :term:`coercion`) to a common type. For example, an integer
|
| /external/python/cpython2/Doc/whatsnew/ |
| D | 2.1.rst | 511 How numeric coercion is done at the C level was significantly modified. This
516 ``PyTypeObject`` structure to indicate that they support the new coercion model.
519 arguments of differing types, and can then perform their own internal coercion.
|
| D | 2.5.rst | 941 is also used to implement coercion to integers. If slicing used
|
| D | 2.7.rst | 772 * Implicit coercion for complex numbers has been removed; the interpreter
|
| /external/python/cpython3/Doc/whatsnew/ |
| D | 2.1.rst | 511 How numeric coercion is done at the C level was significantly modified. This
516 ``PyTypeObject`` structure to indicate that they support the new coercion model.
519 arguments of differing types, and can then perform their own internal coercion.
|
| D | 2.5.rst | 941 is also used to implement coercion to integers. If slicing used
|
| D | 2.7.rst | 787 * Implicit coercion for complex numbers has been removed; the interpreter
|
| /external/python/cpython3/Doc/ |
| D | glossary.rst | 174 coercion
180 will raise a ``TypeError``. Without coercion, all arguments of even
|
| /external/python/cpython2/Doc/library/ |
| D | functions.rst | 957 The arguments must have numeric types. With mixed operand types, the coercion
959 result has the same type as the operands (after coercion) unless the second
1733 type, using the same rules as used by arithmetic operations. If coercion is not
|
| D | string.rst | 272 The *conversion* field causes a type coercion before formatting. Normally, the
|
| D | codecs.rst | 1173 | | | :term:`coercion` between |
|
| /external/python/cpython3/Doc/library/ |
| D | string.rst | 246 The *conversion* field causes a type coercion before formatting. Normally, the
|
| D | functions.rst | 1116 coercion rules for binary arithmetic operators apply. For :class:`int`
1117 operands, the result has the same type as the operands (after coercion)
|
| /external/python/cpython2/Objects/ |
| D | typeobject.c | 4404 coercion func = (coercion)wrapped;
|
| /external/python/cpython2/Misc/ |
| D | NEWS | 6120 - Issue #5211: Implicit coercion for the complex type is now completely
6122 alpha 4, but coercion for rich comparisons was accidentally left in.)
6786 - Issue #5211: The complex type no longer uses implicit coercion in mixed-type
7134 - Issue #1680159: Unicode coercion during an 'in' operation no longer masks the
7135 underlying error when the coercion fails for the left hand operand.
|
| D | HISTORY | 5817 coercion if both arguments have the same type but this type has the
8028 (applying the usual coercion if necessary).
8139 - Extensive changes have been made to the coercion code. This mostly
8141 numerical operators without having to use coercion), but
8142 occasionally, in boundary cases the coercion semantics have changed
8148 - In connection with the coercion changes, a new built-in singleton
12641 when no coercion is possible. This is used to fix a problem where
|
| /external/python/cpython3/Doc/reference/ |
| D | datamodel.rst | 2197 coercion rules would become too complicated).
|
| /external/python/cpython3/Misc/ |
| D | HISTORY | 15047 - Issue #5463: In struct module, remove deprecated float coercion
23201 coercion if both arguments have the same type but this type has the
25407 (applying the usual coercion if necessary).
25518 - Extensive changes have been made to the coercion code. This mostly
25520 numerical operators without having to use coercion), but
25521 occasionally, in boundary cases the coercion semantics have changed
25527 - In connection with the coercion changes, a new built-in singleton
30020 when no coercion is possible. This is used to fix a problem where
|
| /external/jline/src/src/test/resources/jline/example/ |
| D | english.gz | |
| /external/v8/ |
| D | ChangeLog | 22145 Drop thenable coercion cache (Chromium issue 372788).
|
12