2010/3/2 François Bissey <[email protected]>: >> Hi, >> >> Some are known problems due to using different versions of certain >> packages, example: >> >> -%<- >> File "/usr/share/sage/devel/doc/en/numerical_sage/cvxopt.rst", line 57: >> sage: print(A) >> Expected: >> SIZE: (5,5) >> (0, 0) 2.0000e+00 >> (1, 0) 3.0000e+00 >> (0, 1) 3.0000e+00 >> (2, 1) -1.0000e+00 >> (4, 1) 4.0000e+00 >> (1, 2) 4.0000e+00 >> (2, 2) -3.0000e+00 >> (3, 2) 1.0000e+00 >> (4, 2) 2.0000e+00 >> (2, 3) 2.0000e+00 >> (1, 4) 6.0000e+00 >> (4, 4) 1.0000e+00 >> Got: >> [ 2.00e+00 3.00e+00 0 0 0 ] >> [ 3.00e+00 0 4.00e+00 0 6.00e+00] >> [ 0 -1.00e+00 -3.00e+00 2.00e+00 0 ] >> [ 0 0 1.00e+00 0 0 ] >> [ 0 4.00e+00 2.00e+00 0 1.00e+00] >> <BLANKLINE> >> -%<- >> or >> -%<- >> File "/usr/share/sage/devel/sage/sage/libs/pari/gen.pyx", line 6844: >> sage: nf.nfroots(y^2 + 2) >> Expected: >> [-zz, zz] >> Got: >> [Mod(-zz, zz^2 + 2), Mod(zz, zz^2 + 2)] >> -%<- >> >> Some are due to system wide installation, example: >> -%<- >> File "/usr/share/sage/devel/doc/common/builder.py", line 157: >> sage: b = builder.DocBuilder('tutorial') >> Exception raised: >> Traceback (most recent call last): >> File "/usr/share/sage/local/bin/ncadoctest.py", line 1231, in >> run_one_test self.run_one_example(test, example, filename, compileflags) >> File "/usr/share/sage/local/bin/sagedoctest.py", line 38, in >> run_one_example >> OrigDocTestRunner.run_one_example(self, test, example, >> filename, compileflags) >> File "/usr/share/sage/local/bin/ncadoctest.py", line 1172, in >> run_one_example >> compileflags, 1) in test.globs >> File "<doctest __main__.example_4[3]>", line 1, in <module> >> b = builder.DocBuilder('tutorial')###line 157: >> sage: b = builder.DocBuilder('tutorial') >> File "/usr/share/sage/devel/doc/common/builder.py", line 145, in >> __init__ mkdir(os.path.join(self.dir, "static")) >> File "/usr/share/sage/devel/doc/common/builder.py", line 55, in mkdir >> os.makedirs(path) >> File "/usr/lib64/python2.6/os.py", line 157, in makedirs >> mkdir(name, mode) >> OSError: [Errno 13] Permission denied: >> '/usr/share/sage/devel/doc/en/tutorial/static' >> -%<- >> or >> -%<- >> File "/usr/share/sage/devel/doc/en/constructions/plotting.rst", line 209: >> sage: maxima.eval('load("plotdf");') >> Expected: >> '".../local/share/maxima/.../share/dynamics/plotdf.lisp"' >> Got: >> '"/usr/share/maxima/5.20.1/share/dynamics/plotdf.lisp"' >> -%<- >> >> Some are somewhat strange, but I believe they are due to using some >> package with different version, or missing some patch. Examples: >> -%<- >> File "/usr/share/sage/devel/sage/sage/matrix/matrix1.pyx", line 448: >> sage: sorted(numpy.typecodes.items()) >> Expected: >> [('All', '?bhilqpBHILQPfdgFDGSUVO'), ('AllFloat', 'fdgFDG'), >> ('AllInteger', 'bBhHiIlLqQpP'), ('Character', 'c'), ('Complex', >> 'FDG'), ('Float', 'fdg'), ('Integer', 'bhilqp'), ('UnsignedInteger', >> 'BHILQP')] >> Got: >> [('All', '?bhilqpBHILQPfdgFDGSUVOMm'), ('AllFloat', 'fdgFDG'), >> ('AllInteger', 'bBhHiIlLqQpP'), ('Character', 'c'), ('Complex', >> 'FDG'), ('Datetime', 'Mm'), ('Float', 'fdg'), ('Integer', 'bhilqp'), >> ('UnsignedInteger', 'BHILQP')] >> -%<- >> and >> -%<- >> File "/usr/share/sage/devel/sage/sage/sets/set.py", line 312: >> sage: Primes() < Set(QQ) >> Expected: >> True >> Got: >> False >> -%<- >> and >> -%< >> File "/usr/share/sage/devel/sage/sage/finance/time_series.pyx", line 1505: >> sage: finance.TimeSeries([z.hurst_exponent() for z in y]).mean() >> Expected: >> 0.579848225779347... >> Got: >> 0.5798482257793468 >> -%<- >> >> Some details that may be useful: >> 1) I am using a custom cPickle.so and pickle.py in $PYTHONPATH due to >> sage's patches >> 2) I am using a custom sets.py in $PYHTONPATH that doesn't generate a >> DeprecationWarning, >> otherwise, the number of false positive positives due to >> Deprecation warnings is too high... >> 3) I am using gmp5 instead of mpir (needs only a one line patch so far...) >> 4) I am using a newer givaro and python-mpmath, because other packages >> resolved to >> update those packages :-) So, I built a givaro patch, and used >> mpmath patches from trac >> >> >> I also found out that clisp maxima backend has a serious issue, in >> that, for example it hangs >> with the command: >> sage: maxima.eval('x==x') >> (as in sage/interfaces/maxima.py eval_line doctest) >> and, probably because of the timeout and process kill, it causes some >> other weird >> doctest failures like: >> -%<- >> File "/usr/share/sage/devel/sage/sage/symbolic/relation.py", line 560: >> sage: solve([cos(x)*sin(x) == 1/2, x+y == 0],x,y) >> Expected: >> [[x == 1/4*pi + pi*z38, y == -1/4*pi - pi*z38]] >> Got: >> [[x == 1/4*pi + pi*z39, y == -1/4*pi - pi*z39]] >> -%<- >> >> I reported the clisp problem upstream; last response: >> https://sourceforge.net/mailarchive/forum.php?thread_name=4B8D57D2.4080002% >> 40gnu.org&forum_name=clisp-devel but the tests work with other lisp >> backends (only did not yet test gcl from the available backends in >> Mandriva package) >> > Hi Paulo,
Hi François, > Could you send me your test.log in full so we can compare books with > what we are doing in Gentoo? I can send it to you tomorrow (at home now :-) > You are using gmp5, is the patch you mention the xgcd patch? The gmp package doesn't have any patches. The only gmp5 related sage patch is http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/sagemath/current/SOURCES/sage-4.3.3-gmp5.patch?view=markup There is also some small magic in http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/sagemath/current/SPECS/sagemath.spec?revision=513302&view=markup but I don't remember the reason or what it does :-) just search for gmp in the spec file. Also, it is implicitly copying the related files somewhere in %install > We are currently using gmp4, but I am slowly porting stuff to mpir > (yes that means having stuff using mpir.h and libmpir directly, > I got ntl, pari, zn_poly, sage's clib and genus2reduction so far, lcalc > and flint are next) that's a big bag of hurt as you have to get the linking > right (which is why genus2reduction is on the list it links against pari...). > This is of course quite experimental. So far I am trying to avoid such headaches :-) The only package that explicitly requires mpir is Macaulay2, but I patched it to accept gmp... > We are using ecl for maxima now. One thing I have learned about maxima > is that you can build it with several lisp back end _at_the_same_time_. > So my current system install of maxima which is used in sage is built > against both ecl and sbcl. The lisp engine can be changed at runtime > with "maxima -l ecl" or "maxima -l sbcl", we made sure that maxima is > called with the ecl back end - a one line sed patch in the sage spkg. Only today I enabled a ecl backend to Mandriva's version of maxima, and still required the patch described at http://sourceforge.net/tracker/?func=detail&aid=2962219&group_id=30035&atid=398053 (I tried earlier, but after a lot of patching, gave up... maybe should have used sage spkgs instead of upstream of maxima and ecl) > I have pondering that for several days, would you be interested in a > separate mailing list dedicated to porting sage to linux distros > (or more generally to package managers)? It could serve as a point of > contact for testers and developers to share their problems and solutions > which are not suitable for sage-devel. This should be a good idea :-) But unsure if would have much trafic, I remember the xorg packagers list had like only one email per month, and usually spam... Since there isn't much trafic in sage-devel also, probably, both here, irc (I am not always in #sage-devel, but I am also "pcpa" in freenode, when at Mandriva building here in Brasil) or private email should be enough for now. > Would need a good name too Sage-on-Linux-Distros [SoLD] is not that > good and Sage-for-Package-Managers [SPaM] is not terrible either. > I know about debian-sage but it seems to be dead. > > Francois > > -- > To post to this group, send an email to [email protected] > To unsubscribe from this group, send an email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org Paulo -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
