[sage-support] Sage-2.9
Hello, Sage 2.9 has been released. It is available at http://sagemath.org/download.html This is a *major* new release, with a huge number of tickets closed, and the additional of both R and the ATLAS BLAS as standard packages. If you're an *expert* user or just brave, do sage -upgrade but this may yield your sage temporarily unusable -- if that does happen, do email sage-support. If you're a beginner install from source or wait for new binaries to be posted in a few days (or less). --- The following people contributed this release: * Michael Abshoff * Martin Albrecht * Robert Bradshaw * Tom Boothby * Ondrej Certik * Craig Citro * F. Clark * John Cremona * Alyson Deines * Burcin Erocal * Jan Groenewald * David Harvey * Mike Hansen * Josh Kantor * Robert Miller * Bobby Moretti * Rich Morin * Bill Page * Willem Jan Palenstijn * Yi Qiang * David Roe * William Stein * Carl Witty * Paul Zimmermann Cheers, Michael Abshoff (release chair), William Stein * Major Features, New Spkgs and Bugfixes We achieved most of the goals we set ourselves for 2.9. The major changes compared to 2.8.15 are: * Integration of PolyBoRi * Integration of ATLAS BLAS/Lapack on non-OSX * Integration of R 2.6.1 and rpy * Update to FLINT 1.02 * Update to Symmetrica 2.0 * Much faster permutation arithmatic * Very fast rubik's cube solvers * Many build fixes applied and many bugs squashed We closed a total of 110 tickets, for details see below or our tracker at http://www.sagetrac.org/sage_trac/query?status=closed&milestone=sage-2.9 * Known Issues with 2.9 #1137: Import gd fails to import on OSX 10.4 ppc. Any attempt to fix this breaks other applications on different OSX flavors. We hope to fix this in 2.9.1. #1497: ATLAS fails to build on FC7, Dual core [known ATLAS issue with workaround: disable power management] * Upcoming Releases The following releases are planned for the rest of the year: * 2.9.1: chaired by Robert Miller, bug fixes, release planned about a week from now * 2.9.2: chaired by Michael Abshoff, bug fixes, release planned about two weeks from now 2.9.2 will be the release we plan to distribute on DVD at the AMS meeting, so we are shooting hard for an excellent release. * Doctesting Coverage For 2.9: Overall weighted coverage score: 35.3% Total number of functions: 17947 Compared to 2.8.15 this is an increase by 0.5%. * About Sage (http://www.sagemath.org) Sage is developed by volunteers and combines 71 open source packages. It is available for download from sagemath.org and its mirrors in source or binary form. If you have any questions and/or problems please report them to the google groups sage-devel, sage-support, sage-forum or sage-newbie. You can also drop by in #sage-devel in freenode. * Closed Tickets: Merged in rc3: #1529: William Stein: update install_scripts to also install R script. #1530: William Stein: building tut.tex is currently broken #1531: Michael Abshoff: fix doctest failure sage/calculus/calculus.py #1532: Josh Kantor; Michael Abshoff: Error out with intelligent message if ATLAS tune failed Without tickets: William Stein: update libpng.spkg William Stein: don't let "sage -ba" start sage William Stein: link libcsage.so against atlas on non-OSX William Stein: link IML against atlas on non-OSX Willaim Stein, Michael Abshoff: Various doctest fixes Michael Abshoff: link LinBox against atlas on non-OSX Michael Abshoff: remove forced check from FLINT.spkg Merged in rc1/2: #1258: Willem Jan Palenstijn, Robert Miller: additions and changes to linear_codes #1457: William Stein: "BUG: Rational.__pow__ called on a non-Rational" #1464: Robert Miller: binary code canonical labels & automorphism group generators #1503: William Stein: formal function calls don't coerce correctly to Mathematica #1511: Robert Bradshaw: Export 3d objects in jmol format #1527: William Stein: doctest R with "import rpy" #1528: William Stein: make "sage -R" run R. Merged in rc0: #444: Robert Bradshaw: solve the rubik's cube fast! #553: Mike Hansen, William Stein: calling of symbolic expressions is sometimes ridiculous #1077: Yi Qiang: DSage restarts two workers after timeout, various other fixes and improvements #1119: Martin Albrecht, Robert Bradshaw: EllipticCurve.random_element for char=2 #1137: Robert Miller: matrix visualize_structure is completely broken on OSX [later reverted] #1162: Paul Zimmermann, Carl Witty: fix issues in RealField <-> RQDF conversions #1183: David Roe, William Stein, Alyson Deines: Residue fields are broken. This patch set also fixes #1242 and #1185 #1232: Craig Citro: bug in modular symbols over GF(2) #1237: David Roe: E.torsion_order() fails on curves with big coefficients! #1239: Robert Bradshaw, John Cremona: Wrap Simon's new gp two descent code #1393: Robert Miller: is_integral_domain
[sage-support] Compilation issue on MacOSX 10.4.11
Hi all, I am trying to install Sage 2.9 from sources and am running into some trouble with gmp and pari. I know nothing has been changed from right before, and indeed I had the same problem when I tried (and gave up) to install 2.8.15. I think the last version of Sage I had was 2.8.5 My install log is at http://math.stanford.edu/~pdehaye/install.log.gz The offending lines are gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -fno-gcse- after-reload -I. -I../src/headers -I../src/graph -o plotport.o ../ src/graph/plotport.c gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -fno-gcse- after-reload -I. -I../src/headers -o plotnull.o ../src/graph/ plotnull.c cat ../src/kernel/gmp/mp.c ../src/kernel/none/cmp.c ../src/kernel/none/ gcdll.c ../src/kernel/none/ratlift.c ../src/kernel/none/invmod.c ../ src/kernel/gmp/gcd.c ../src/kernel/none/mp_indep.c ../src/kernel/none/ add.c > mp.c gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -fno-gcse- after-reload -fno-common -I. -I../src/headers -o mp.o mp.c ../src/kernel/gmp/mp.c:43:17: error: gmp.h: No such file or directory ../src/kernel/gmp/mp.c: In function 'pari_kernel_init': ../src/kernel/gmp/mp.c:55: warning: implicit declaration of function 'mp_set_memory_functions' ../src/kernel/gmp/mp.c: At top level: ../src/kernel/gmp/mp.c:66: error: parse error before '*' token ../src/kernel/gmp/mp.c: In function 'xmpn_copy': ../src/kernel/gmp/mp.c:68: error: 'n' undeclared (first use in this function) ../src/kernel/gmp/mp.c:68: error: (Each undeclared identifier is reported only once ../src/kernel/gmp/mp.c:68: error: for each function it appears in.) ../src/kernel/gmp/mp.c:68: error: 'x' undeclared (first use in this function) ../src/kernel/gmp/mp.c:68: error: 'y' undeclared (first use in this function) [LOTS OF ERRORS] make[3]: *** [mp.o] Error 1 make[2]: *** [gp] Error 2 Error building GP real0m13.247s user0m8.473s sys 0m3.813s sage: An error occurred while installing pari-2.3.2.p4 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of /Library/sage-2.9/install.log. Describe your computer, operating system, etc. If you want to try to fix the problem, yourself *don't* just cd to /Library/sage-2.9/spkg/build/pari-2.3.2.p4 and type 'make'. Instead type "/Library/sage-2.9/sage -sh" in order to set all environment variables correctly, then cd to /Library/sage-2.9/spkg/build/pari-2.3.2.p4 (When you are done debugging, you can type "exit" to leave the subshell.) make[1]: *** [installed/pari-2.3.2.p4] Error 1 I am running gcc 4.0.1 Any help appreciated! Paul --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: Sage-2.9
Just finished building it... it took over 7hours on my machine, but it was worth it :)... btw - both 2 things about R are still actual in 2.9, that's "_" -> "." change for rpy to report version, and some comments to enable optional package installation... apart from that it is sweet :)... congratulations :) btw... it's known that plotting in R doesn't work well yet, right? using png() & dev.off() produces images with those numbers on it, and using straight plot/hist from R, opens up X11 window with plot (those numbers are also on it... I can make screenshot of it in X11 window if it can help) regards, Andrzej. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Fwd: [sage-newbie] Re: Loading data files (say csv or text) into Sage
Hi, Could someone with a Windows machine make an entry in the documentation or on the FAQ about how to share files between the Ubuntu virtual machine and the host Windows operating system? Maybe with screenshots? (see email below) -- Carlo -- Forwarded message -- From: Carlo Hamalainen <[EMAIL PROTECTED]> Date: Dec 17, 2007 9:26 AM Subject: Re: [sage-newbie] Re: Loading data files (say csv or text) into Sage To: [EMAIL PROTECTED] On Dec 17, 2007 8:51 AM, Lyndon <[EMAIL PROTECTED]> wrote: > Do I need to put the files to attach and open into a particular > folder? I keep getting a "no such file or directory" message when I > use attach or reader.csv (I have tried the full path names and > different folders/drives). I'm using a windows machine but can only > find help for unix based systems. I believe that the easiest way is to share a folder on your Windows computer and then mount it from the Ubuntu virtual machine (the filesystem that Sage runs on is an image file for vmware so Windows can't peek inside directly). Here are some instructions that should work: http://mytechnotes.wordpress.com/2007/05/21/windows-shared-folder-from-ubuntu/ I'll forward you question to sage-devel because there really should be a step by step guide with screenshots for sharing files. (I would have done it myself this morning but I don't have a Windows PC here). --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: [sage-newbie] Re: Loading data files (say csv or text) into Sage
On Dec 16, 2007 2:51 PM, Lyndon <[EMAIL PROTECTED]> wrote: > > Thanks for that. One more (well hopefully only one) dumb question. > > Do I need to put the files to attach and open into a particular > folder? I keep getting a "no such file or directory" message when I > use attach or reader.csv (I have tried the full path names and > different folders/drives). I'm using a windows machine but can only > find help for unix based systems. I assume you're using sage-vmware. Anyways, do the following: (1) Open a worksheet (2) Select Data --> "Upload or create file..." (3) Click Browse and select your file (under Windows). (4) Click "Upload file"; wait as your file is loaded into that Sage worksheet. (5) If the file is called "foo.data", you can now use it from the SAGE notebook by calling it DATA+'foo.data', e.g., to view it do print open(DATA+'foo.data').read() (6) You can view your file by going to Data ... --> foo.data NOTE -- if you change the file under Windows you have to upload it again in order for Sage to see the changes. If you want Sage to instantly see a file that is under Windows you have to somehow mount the Windows partition in vmware as explained in the other answer to your email. One advantage of what is described above is it will work in exactly the same with any Sage notebook server either on some remote machine or on your computer. Also, it is easy and will "Just work", whereas mounting windows files is potentially complicated, and possibly even dangerous, since it means that Sage has access to your windows files (which it does *not* by default -- a nice security precaution). FAQ maintainer -- this should be in the faq. > > cheers. > > > > On Dec 15, 10:20 pm, "Carlo Hamalainen" <[EMAIL PROTECTED]> > wrote: > > On Dec 14, 2007 1:08 PM, Lyndon <[EMAIL PROTECTED]> wrote: > > > > > I have some big datasets in SAS, which can be exported as CSV or text > > > or whatever. Is it possible to load these into Sage? If so, how do > > > you go about it? > > > > Sage uses Python as the underlying language, so you can start by > > looking at the IO section of the Python > > Tutorial:http://docs.python.org/tut/node9.html > > (also read about pickling/unpickling) > > > > To save reinventing the wheel, Python has a module for dealing with CSV > > files:http://docs.python.org/lib/module-csv.html > > > > Some examples of reading CSV > > files:http://docs.python.org/lib/csv-examples.html > > > > You can paste those examples into blah.sage and then run the file from > > a notebook or do > > > > sage:attach'blah.sage' > > > > at the command line. > > > > > Is this the kind of thing that one could code up in Sage? > > > > Yep :) > > > > -- > > Carlo Hamalainenhttp://carlo-hamalainen.net > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] SAGE v2.9 - make pdf - style file too long error
I'm new to SAGE and to this support group so I hope I am asking the right question in the right area. I am trying to package SAGE v2.9 for PCLinuxOS (an up-and-coming Linux distribution). My first question is actually a problem I ran into when trying to make PDF documentation. After changing directories to devel/doc I ran make PDF. This complained at me that some python module was not available. So, I changed the Makefile to use sage-python instead of the default python. This made the documentation build process go a lot farther, but it still failed with the following error. I'm not too familiar with makeindex, so I don't understand the error. Can someone please guide me along here? Thanks in advance! P.S. on a side note, does anyone know where I can find an SRPM or just a SPEC file for SAGE from some other distribution (Mandriva or RedHat perhaps?) make pdf cd paper-letter && TEXINPUTS=/home/gri6507/src/rpm/BUILD/sage-2.9/ devel/doc-main/commontex: sage-python /home/gri6507/src/rpm/BUILD/ sage-2.9/devel/doc-main/tools/mkhowto --paper=letter --pdf ../ref/ ref.tex +++ TEXINPUTS=/home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/ref:/ home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/commontex:/home/ gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/paper-letter:/home/ gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/texinputs: +++ pdflatex ref +++ makeindex ref.idx +++ pdflatex ref +++ makeindex -s /home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/ texinputs/python.ist ref.idx *** Session transcript and error messages are in /home/gri6507/src/rpm/ BUILD/sage-2.9/devel/doc-main/paper-letter/ref.how. *** Exited with status 1. The relevant lines from the transcript are: +++ makeindex -s /home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/ texinputs/python.ist ref.idx Style file /home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/ texinputs/python.ist too long. Usage: makeindex [-ilqrcgLT] [-s sty] [-o ind] [-t log] [-p num] [idx0 idx1 ...] *** Session transcript and error messages are in /home/gri6507/src/rpm/ BUILD/sage-2.9/devel/doc-main/paper-letter/ref.how. *** Exited with status 1. make: *** [paper-letter/ref.pdf] Error 1 --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: SAGE v2.9 - make pdf - style file too long error
On Dec 16, 2007 9:31 PM, gri6507 <[EMAIL PROTECTED]> wrote: > > I'm new to SAGE and to this support group so I hope I am asking the > right question in the right area. I am trying to package SAGE v2.9 for > PCLinuxOS (an up-and-coming Linux distribution). My first question is > actually a problem I ran into when trying to make PDF documentation. > > After changing directories to devel/doc I ran make PDF. This > complained at me that some python module was not available. So, I > changed the Makefile to use sage-python instead of the default python. > This made the documentation build process go a lot farther, but it > still failed with the following error. I'm not too familiar with > makeindex, so I don't understand the error. Can someone please guide > me along here? Thanks in advance! To make the pdf of const.tex, you can cd to sage-2*/devel/doc/const and type build_pdf. This sets the environment variables properly. > > P.S. on a side note, does anyone know where I can find an SRPM or just > a SPEC file for SAGE from some other distribution (Mandriva or RedHat > perhaps?) > > make pdf > cd paper-letter && TEXINPUTS=/home/gri6507/src/rpm/BUILD/sage-2.9/ > devel/doc-main/commontex: sage-python /home/gri6507/src/rpm/BUILD/ > sage-2.9/devel/doc-main/tools/mkhowto --paper=letter --pdf ../ref/ > ref.tex > +++ TEXINPUTS=/home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/ref:/ > home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/commontex:/home/ > gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/paper-letter:/home/ > gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/texinputs: > +++ pdflatex ref > +++ makeindex ref.idx > +++ pdflatex ref > +++ makeindex -s /home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/ > texinputs/python.ist ref.idx > *** Session transcript and error messages are in /home/gri6507/src/rpm/ > BUILD/sage-2.9/devel/doc-main/paper-letter/ref.how. > *** Exited with status 1. > The relevant lines from the transcript are: > > +++ makeindex -s /home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/ > texinputs/python.ist ref.idx > Style file /home/gri6507/src/rpm/BUILD/sage-2.9/devel/doc-main/ > texinputs/python.ist too long. > Usage: makeindex [-ilqrcgLT] [-s sty] [-o ind] [-t log] [-p num] [idx0 > idx1 ...] > *** Session transcript and error messages are in /home/gri6507/src/rpm/ > BUILD/sage-2.9/devel/doc-main/paper-letter/ref.how. > *** Exited with status 1. > make: *** [paper-letter/ref.pdf] Error 1 > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: Sage-2.9
> Sage 2.9 has been released. It is available at > >http://sagemath.org/download.html > > So this built with no reported errors on my Mac Pro (Intel, 10.4.11). However, make check reported one error: sage -t devel/sage-main/sage/stats/test.py ** File "test.py", line 5: sage: import rpy Exception raised: Traceback (most recent call last): File "/Users/craigcitro/sage-2.9/local/lib/python2.5/doctest.py", line 1212, in __run compileflags, 1) in test.globs File "", line 1, in import rpy###line 5: sage: import rpy ImportError: No module named rpy ** 1 items had failures: 1 of 1 in __main__.example_0 ***Test Failed*** 1 failures. Looking at the install.log, it turns out that rpy failed to build, but this error wasn't propogated back to the r-2.6.1.p6 make process. So there are two issues: 1) Why did rpy fail? 2) Should this stop the build of R, or at least inform the user more noticeably? For (1), the answer was easy: the rpy setup.py uses "tail -1" for "tail -n 1", which fails on some systems (namely mine). I'm running the most current version of textutils: [EMAIL PROTECTED] ~/sage-2.9/spkg/standard] $ tail --version tail (textutils) 2.1 Written by Paul Rubin, David MacKenzie, Ian Lance Taylor, and Jim Meyering. Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. That's the most recent version according to the webpage, but the same version is installed on sage.math, where tail -1 works just fine. (This might have to do with the POSIX settings when tail was compiled? I vaguely got this impression from the FAQ on the textutils webpage.) So I'll report this upstream, but I suspect I should also add a patch to the rpy-1.0.1.spkg we ship, because I doubt I'm the only one with this issue. This is now trac ticket #1543, with a new rpy-1.0.1.spkg attached (since there's no mercurial repository in the spkg). 2) I would assume that we should halt the build if rpy fails for any reason; this is a simple 3-line fix in spkg-install, which I'm going to post on trac right now. (...) It's trac ticket #1542, with the simple patch attached. -cc --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: Sage-2.9
On Dec 16, 2007 11:04 AM, William Stein <[EMAIL PROTECTED]> wrote: > > Hello, > > Sage 2.9 has been released. It is available at > >http://sagemath.org/download.html > > This is a *major* new release, with a huge number of tickets > closed, and the additional of both R and the ATLAS BLAS > as standard packages. > > If you're an *expert* user or just brave, do > >sage -upgrade I had no serious problem with this on a 64 bit ubuntu machine. However, it did open up a file emacs (yeah:-), as though it was doing a hg_sage.commit(). I just got out of emacs without saving, aborting something I guess, and it continued with the upgrade. > > but this may yield your sage temporarily unusable -- if that does happen, > do email sage-support. > > If you're a beginner install from source or wait for new > binaries to be posted in a few days (or less). > > --- > > The following people contributed this release: > > * Michael Abshoff > * Martin Albrecht > * Robert Bradshaw > * Tom Boothby > * Ondrej Certik > * Craig Citro > * F. Clark > * John Cremona > * Alyson Deines > * Burcin Erocal > * Jan Groenewald > * David Harvey > * Mike Hansen > * Josh Kantor > * Robert Miller > * Bobby Moretti > * Rich Morin > * Bill Page > * Willem Jan Palenstijn > * Yi Qiang > * David Roe > * William Stein > * Carl Witty > * Paul Zimmermann > > Cheers, > > Michael Abshoff (release chair), William Stein > > * Major Features, New Spkgs and Bugfixes > > We achieved most of the goals we set ourselves for 2.9. The major > changes compared to 2.8.15 are: > > * Integration of PolyBoRi > * Integration of ATLAS BLAS/Lapack on non-OSX > * Integration of R 2.6.1 and rpy > * Update to FLINT 1.02 > * Update to Symmetrica 2.0 > * Much faster permutation arithmatic > * Very fast rubik's cube solvers > * Many build fixes applied and many bugs squashed > > We closed a total of 110 tickets, for details see below or our > tracker at > > http://www.sagetrac.org/sage_trac/query?status=closed&milestone=sage-2.9 > > * Known Issues with 2.9 > > #1137: Import gd fails to import on OSX 10.4 ppc. Any attempt >to fix this breaks other applications on different OSX >flavors. We hope to fix this in 2.9.1. > #1497: ATLAS fails to build on FC7, Dual core [known ATLAS >issue with workaround: disable power management] > > * Upcoming Releases > > The following releases are planned for the rest of the year: > > * 2.9.1: chaired by Robert Miller, bug fixes, release > planned about a week from now > * 2.9.2: chaired by Michael Abshoff, bug fixes, release > planned about two weeks from now > > 2.9.2 will be the release we plan to distribute on DVD at the AMS > meeting, so we are shooting hard for an excellent release. > > * Doctesting Coverage > > For 2.9: > > Overall weighted coverage score: 35.3% > Total number of functions: 17947 > > Compared to 2.8.15 this is an increase by 0.5%. > > * About Sage (http://www.sagemath.org) > > Sage is developed by volunteers and combines 71 open source packages. > It is available for download from sagemath.org and its mirrors in > source or binary form. If you have any questions and/or problems > please report them to the google groups sage-devel, sage-support, > sage-forum or sage-newbie. You can also drop by in #sage-devel in > freenode. > > * Closed Tickets: > > Merged in rc3: > > #1529: William Stein: update install_scripts to also install R script. > #1530: William Stein: building tut.tex is currently broken > #1531: Michael Abshoff: fix doctest failure sage/calculus/calculus.py > #1532: Josh Kantor; Michael Abshoff: Error out with intelligent >message if ATLAS tune failed > > Without tickets: > > William Stein: update libpng.spkg > William Stein: don't let "sage -ba" start sage > William Stein: link libcsage.so against atlas on non-OSX > William Stein: link IML against atlas on non-OSX > Willaim Stein, Michael Abshoff: Various doctest fixes > Michael Abshoff: link LinBox against atlas on non-OSX > Michael Abshoff: remove forced check from FLINT.spkg > > Merged in rc1/2: > > #1258: Willem Jan Palenstijn, Robert Miller: additions and changes >to linear_codes > #1457: William Stein: "BUG: Rational.__pow__ called on a non-Rational" > #1464: Robert Miller: binary code canonical labels & automorphism >group generators > #1503: William Stein: formal function calls don't coerce correctly to >Mathematica > #1511: Robert Bradshaw: Export 3d objects in jmol format > #1527: William Stein: doctest R with "import rpy" > #1528: William Stein: make "sage -R" run R. > > Merged in rc0: > > #444: Robert Bradshaw: solve the rubik's cube fast! > #553: Mike Hansen, William Stein: calling of symbolic expressions is > sometimes ridiculous > #1077: Yi Qiang: DSage restarts two workers after timeout, various >other fixes and improvements > #1119: Martin Albrecht, Robert Bradshaw: EllipticCurve.random_eleme
[sage-support] Re: Sage-2.9
On Dec 17, 3:58 am, "Craig Citro" <[EMAIL PROTECTED]> wrote: > > Sage 2.9 has been released. It is available at > > >http://sagemath.org/download.html > > So this built with no reported errors on my Mac Pro (Intel, 10.4.11). > However, make check reported one error: > > sage -t devel/sage-main/sage/stats/test.py > ** > File "test.py", line 5: > sage: import rpy > Exception raised: > Traceback (most recent call last): > File "/Users/craigcitro/sage-2.9/local/lib/python2.5/doctest.py", > line 1212, in __run > compileflags, 1) in test.globs > File "", line 1, in > import rpy###line 5: > sage: import rpy > ImportError: No module named rpy > ** > 1 items had failures: >1 of 1 in __main__.example_0 > ***Test Failed*** 1 failures. > > Looking at the install.log, it turns out that rpy failed to build, but > this error wasn't propogated back to the r-2.6.1.p6 make process. So > there are two issues: > > 1) Why did rpy fail? > 2) Should this stop the build of R, or at least inform the user more > noticeably? > > For (1), the answer was easy: the rpy setup.py uses "tail -1" for > "tail -n 1", which fails on some systems (namely mine). I'm running > the most current version of textutils: > > [EMAIL PROTECTED] ~/sage-2.9/spkg/standard] $ tail --version > tail (textutils) 2.1 > Written by Paul Rubin, David MacKenzie, Ian Lance Taylor, and Jim Meyering. > > Copyright (C) 2002 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > That's the most recent version according to the webpage, but the same > version is installed on sage.math, where tail -1 works just fine. > (This might have to do with the POSIX settings when tail was compiled? > I vaguely got this impression from the FAQ on the textutils webpage.) > So I'll report this upstream, but I suspect I should also add a patch > to the rpy-1.0.1.spkg we ship, because I doubt I'm the only one with > this issue. This is now trac ticket #1543, with a new rpy-1.0.1.spkg > attached (since there's no mercurial repository in the spkg). > > 2) I would assume that we should halt the build if rpy fails for any > reason; this is a simple 3-line fix in spkg-install, which I'm going > to post on trac right now. (...) It's trac ticket #1542, with the > simple patch attached. > Hi Craig, as just mentioned in IRC I will review those patches/spkgs tonight [my tonight since it is very early here at the moment] and I think rlm should stick those in 2.9.1. We just need to bumb the version number of rpy and as you observed fix the rpy.spkg name in the R.spkg itself, too. > -cc Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: Sage-2.9
Hello, I ran sage "-testall -long" and sage "-testall -optional" on the 2.9 release on sage.math. While -long passed with flying colors, -optional had some failures in tut.tex since I didn't install some optional GAP database. But there are also some problems with maxima, which might just be fallout from the GAP failure. I will investigate, but it seems that we are in reasonably good shape [William had feared that loads of things would go *boom*]. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
