> Em 8 de novembro de 2011 04:20, Paulo César Pereira de Andrade > > <paulo.cesar.pereira.de.andr...@gmail.com> escreveu: > > 2011/11/7 Francois Bissey <francois.bis...@canterbury.ac.nz>: > >> Hi Paulo, > >> > >> You are using python-2.7 right? In #9958 I have a list of patches > >> as long as my arm to deal with the numerical noise and changes > >> in warnings. > > > > Yes, python 2.7.2. Thanks for the hint on the patches. They appear > > to address exactly a good share of the doctest failures I noticed. > >
The patch there were made against 2.7.1 there are a couple of differene and extra things with 2.7.2 but that should considerably reduce the number of failures. > >> For mpmath/sympy in gentoo we are now using sympy-0.7.1 with > >> the patches I wrote. This will land in sage-4.8.0 proper. Now for > >> Gentoo I wrote a sympy package in which I removed mpmath and > >> forced sympy to use the system mpmath. > >> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev- > >> python/sympy/sympy-0.7.1.ebuild?revision=1.2&view=markup > >> and: > >> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev- > >> python/sympy/files/sympy-0.7.1-mpmath.patch?revision=1.1&view=markup > > > > I am going to use these patches also. > > With the sympy/mpmath patches, I can drop a hack I have been rediff'ing > for some time, but anything that uses mpmath now shows a lot of warnings > like these: > > sage -t -force_lib "devel/sage/sage/libs/mpmath/ext_main.pyx" > *** glibc detected *** python: realloc(): invalid pointer: > 0x0000000003b4d3c0 *** > ... > *** glibc detected *** python: realloc(): invalid pointer: > 0x00000000042465c0 *** > *** glibc detected *** python: free(): invalid pointer: 0x0000000003b4d3a0 > *** *** glibc detected *** python: free(): invalid pointer: > 0x00000000035c86f0 *** [3.8 s] > > Previously there was only one test case with this behavior, but now it > works with some test cases that would fail, most notably this: > TypeError: object.__new__(sage.libs.mpmath.ext_main.mpc) is not > safe, use sage.libs.mpmath.ext_main.mpc.__new__() > that now works. > > But this one got a lot larger numeric variation, now: > File "/usr/share/sage/devel/sage/sage/libs/mpmath/utils.pyx", line 367: > sage: a.call(a.polylog, 2, 1/3+4/5*I) > Expected: > 0.153548951541433 + 0.875114412499637*I > Got: > 0.254715070352197 + 0.874801794256724*I > and before: > > File "/usr/share/sage/devel/sage/sage/libs/mpmath/utils.pyx", line 367: > sage: a.call(a.polylog, 2, 1/3+4/5*I) > Expected: > 0.153548951541433 + 0.875114412499637*I > Got: > 0.159841737717642 + 0.875386092681844*I > I don't get any of that. I suspect there may be an issue with gmp/mpir. But I have really no clue about the glibc problem, you are using mpmath-0.17 I expect. Francois This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
