Home
last modified time | relevance | path

Searched refs:__coerce__ (Results 1 – 11 of 11) sorted by relevance

/external/python/cpython2/Lib/test/
Dtest_coercion.py14 def __coerce__(self, other): member in CoerceNumber
24 def __coerce__(self, other): member in CoerceTo
326 def __coerce__(self, other): member in CoercionTest.test_infinite_rec_classic_classes.Tester
Dtest_compare.py15 def __coerce__(self, other): member in Coerce
Dtest_complex.py121 self.assertRaises(OverflowError, complex.__coerce__, 1+1j, 1L<<10000)
126 def __coerce__(self, other): member in ComplexTest.test_no_implicit_coerce.A
Dtest_class.py80 def __coerce__(self, *args): member in AllTests
Dtest_builtin.py237 def __coerce__(self, other): member in BuiltinTest.test_coerce.BadNumber
/external/python/cpython2/Demo/classes/
Dbitvec.py316 def __coerce__(self, otherseq, *rest): member in BitVec
/external/python/cpython2/Doc/reference/
Ddatamodel.rst1869 :meth:`__coerce__` or other numerical operators. It is recommended that both
2234 .. method:: object.__coerce__(self, other)
2271 :meth:`__coerce__` method in response to a binary operator; the only time
2272 :meth:`__coerce__` is invoked is when the built-in function :func:`coerce` is
2343 All these types implement a :meth:`__coerce__` method, for use by the built-in
2348 The complex type no longer makes implicit calls to the :meth:`__coerce__`
/external/python/cpython2/Doc/whatsnew/
D2.2.rst333 when it checks for other methods such as :meth:`__repr__` or :meth:`__coerce__`,
D2.7.rst773 will no longer ever attempt to call a :meth:`__coerce__` method on complex
/external/python/cpython2/Misc/
Dcheatsheet1203 coerce(s,o) = __coerce__(s,o)
DHISTORY564 - Bug #992017: A classic class that defined a __coerce__() method that returned
8420 - A bug that caused crashes when __coerce__ was used with augmented
15160 - The __coerce__ and __cmp__ methods for user-defined classes once
15271 with __coerce__ method. Also have a look at the end of the Tutorial