On Feb 4, 10:01 pm, ross k <[email protected]> wrote: > So do we...? > 1) download the mpmath-0.14.spkg via the link > 2) cd $SAGE_ROOT > 3) ./sage -f <path-to>mpmath-0.14.spkg
yes - and look out for compile errors, strange warnings, ... > 4) ./sage -hg qimport > http://trac.sagemath.org/sage_trac/attachment/ticket/8159/mpmath_cyth... nearly. here is a good page explaining you the workflow in detail: http://wiki.sagemath.org/MercurialQueues right next to the patch links, there is a tiny download icons. copy the url from there. so, it's setting up .hgrc and qinit (once), hg qpop -a to empty your queue, qimport (twice, since there is a second patch on that ticket) 2x hg qpush to apply them ... hg qseries should list two applied patches now! (if you do not have hg, you can use ./sage -hg <commands ...>) 5) $ ./sage -br #that b_uilds and r_uns sage ... it will compile the cython files that were modified by the two patches above. 6) test the mpmath spkg: inside sage: import mpmath; mpmath.runtests(); mpmath.doctest() ... if there are problems, they are for fredrik. 7) test the sage library $ ./sage -t devel/sage-main/sage/ #that tests all .py(x) files in all directories that are below the given one. when you look at my reply at the ticket there were two places in the sage library that were broken, and hence the second patch to correct this. These are the files that wrap mpmath and expose it in sage. For example, if you call Ei(...), it accesses mpmath and that is tested in such a file there. To speed things up you can just call the tests on those two files [but who knows if mpmath is called somewhere else ... ;) ] Thanks for reviewing, it's a confusing process at the beginning but necessary to keep a decent level of quality! H -- 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
