From: Alex M. <al...@us...> - 2005-11-13 01:27:21
|
Update of /cvsroot/gmpy/gmpy/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3420/doc Modified Files: gmpydoc.txt Log Message: Removed test warning about known scan0/scan1 bugs on Windows (apparently not around any more, yay); edited docs for version 1.01. Index: gmpydoc.txt =================================================================== RCS file: /cvsroot/gmpy/gmpy/doc/gmpydoc.txt,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** gmpydoc.txt 12 Nov 2005 00:04:45 -0000 1.5 --- gmpydoc.txt 13 Nov 2005 01:27:12 -0000 1.6 *************** *** 5,58 **** *Notes on history of file gmpydoc.txt* ! Notes for version 0.1 (pre-alpha), first one placed on ! sourceforge -- A. Martelli, al...@ya..., 00/11/06. ! Edited for version 0.2 (still pre-alpha), bugfixes & ! minor performance tweaks, 00/11/15 -- many thanks to ! Pearu Peterson for his contributions re 0.1 -> 0.2! ! Edited for version 0.3 (ditto) -- cleanup, exposing [...1447 lines suppressed...] ! Basically, this works around Python's (excellent!) choice to adopt ! the terminating-model rather than the restartable one for ! exception handling, in a few cases of specific interest to numeric ! computation that's being used in a symbolic setting. ! Most callbacks are module-global, with one specific exception. ! When any gmpy function or method is trying to convert arguments to ! gmpy objects (mpz, mpq, mpf), and a conversion fails, all argument ! objects are examined, looking for a method called '__gmpy__' in ! any of them. ! If one is found, then, rather than raising an error to indicate ! the conversion failure, that method is called as a 'localized ! callback' as above. This lets other, non-gmpy objects participate ! in gmpy computations (if they're willing to handle all cases ! involving them!): Python does much of this via __coerce__ etc, and ! this localized-callback facility does the rest for named ! module-functions and methods, where normal coercion would not ! apply. |