sage-4.7.1.alpha4 released
Jeroen Demeyer
We're releasing Sage 4.7.1.alpha4.
Source archive:
http://boxen.math.washington.edu/home/release/sage-4.7.1.alpha4/sage-4.7.1.alpha4.tar
Upgrade path:
http://boxen.math.washington.edu/home/release/sage-4.7.1.alpha4/sage-4.7.1.alpha4/
Please build, test, and report! We'd love to hear about your
experiences with this release.
== Tickets ==
* We closed 185 tickets in this release. For details, see
http://boxen.math.washington.edu/home/release/sage-4.7.1.alpha4/tickets.html
Closed tickets:
#4229: special functions should use mpfr when available [Reviewed by
Burcin Erocal, Karl-Dieter Crisman]
#5960: fix bug in documentation of find_minimum_on_interval [Reviewed by
Karl-Dieter Crisman, Burcin Erocal]
#9724: Sage allows creation of variables with empty name [Reviewed by
Volker Braun, Mariah Lenox]
#10550: integration not working [Reviewed by Karl-Dieter Crisman, Burcin
Erocal]
#10945: Fix lots of minor docs and redundancy for riemann.pyx [Reviewed
by Karl-Dieter Crisman]
Merged in sage-4.7.1.alpha4:
#8345: Burcin Erocal: cannot convert symbolic functions back from maxima
[Reviewed by Karl-Dieter Crisman]
#9240: Tom Coates, Burcin Erocal: applying full_simplify() to gamma
functions causes an error [Reviewed by Dan Drake, Karl-Dieter Crisman,
François Bissey]
#9310: Volker Braun: sage-4.4.4.alpha1 build issue -- random doctest
failure on menas (skynet) [Reviewed by Mariah Lenox]
#9333: John Palmieri: the kash optional spkg doesn't work at all on OS X
due to mistake in use of tar [Reviewed by Karl-Dieter Crisman]
#9378: Rakhim Davletkaliyev, Temirlan Kumargazhin, Harald Schilly,
Vladimir Smolyar, Jeroen Demeyer: Russian translation of the Sage
tutorial [Reviewed by Karl-Dieter Crisman, Andrey Novoseltsev]
#9483: Carl Witty: implicit_plot3d fails on symbolic inputs that can't
be automatically differentiated [Reviewed by Karl-Dieter Crisman]
#9560: Burcin Erocal: Symbolic expressions don't do arithmetic with
bools nicely [Reviewed by Karl-Dieter Crisman]
#9989: Burcin Erocal: easier access to operands of a symbolic expression
[Reviewed by Robert Bradshaw, Karl-Dieter Crisman, Volker Braun]
#10529: Volker Braun: dimension() and is_smooth() for algebraic
subschemes of toric varieties [Reviewed by Andrey Novoseltsev]
#10540: Volker Braun: Spec and patches for singular affine toric
varieties / algebraic schemes [Reviewed by Andrey Novoseltsev]
#10587: Sebastian Pancratz: Cleaning up sage.structure.Factorization
[Reviewed by Geoff Ehrman, Marco Streng]
#10645: Paul Mercat: Bug in documentation for class lazy_format
[Reviewed by Mariah Lenox, Jeroen Demeyer]
#10859: Volker Braun: Add is_series() method and others to symbolic
expressions [Reviewed by Karl-Dieter Crisman, Burcin Erocal]
#10860: Andrzej Giniewicz: R package documentation not accessible from
notebook [Reviewed by Karl-Dieter Crisman]
#10873: Robert Bradshaw: Bug in integer_mod powering non-invertible base
and negative exponents [Reviewed by Mariah Lenox]
#10944: Rob Beezer: Check for similar matrices [Reviewed by Dan Drake]
#10964: Richard Kreckel, Burcin Erocal: bug with conjugate in symbolic
ring [Reviewed by Karl-Dieter Crisman]
#10999: John Cremona: Elliptic curve generators from the database lie on
the wrong curve [Reviewed by Jamie Weigandt, Marco Streng]
#11138: Taylor Dupuy: Make Jacobi symbol [Reviewed by François Bissey,
Karl-Dieter Crisman]
#11186: Johan S. R. Nielsen: Missing parentheses when typesetting
coefficients of multivariate polynomials over number fields [Reviewed by
Mariah Lenox]
#11216: Mariah Lenox: Metaticket - make Sage work with gcc 4.6.0
[Reviewed by Jeroen Demeyer]
#11307: Francis Clarke: L rel. number field, E/L ell. curve, P in E(L),
'P in E.base_ring()' -> AttributeError [Reviewed by Marco Streng]
#11352: Richard Kreckel, Jens Vollinga, Burcin Erocal: is_polynomial
returns wrong results [Reviewed by Karl-Dieter Crisman]
#11377: François Bissey: Clean and harmonize module_list.py [Reviewed by
Volker Braun]
#11393: Jason Grout: Teach html.table to take a header row in the header
option [Reviewed by Karl-Dieter Crisman]
#11415: Richard Kreckel, Jens Vollinga, Burcin Erocal: update pynac to
0.2.3 [Reviewed by Karl-Dieter Crisman, François Bissey]
#11419: Nils Bruin: relocation not working for sage-4.7.1.alpha1
[Reviewed by Mariah Lenox]
#11430: Igor Tolkov: is_pseudoprime_small_power has bugs with
get_data=True [Reviewed by Mariah Lenox]
#11449: Jeroen Demeyer: Do not make sage-env executable [Reviewed by
Mariah Lenox]
#11452: William Stein: serious (but trivial to fix) bug in hidden markov
model "generate sequence" function [Reviewed by Bill Cauchois]
#11467: Mike Hansen: Add sage/parallel/* to the reference manual
[Reviewed by Karl-Dieter Crisman]
#11481: Volker Braun: LLL for degenerate matrices crashes [Reviewed by
Robert Bradshaw]
#11491: Ryan Grout: Minor doc formatting problem in tachyon_repr
[Reviewed by Karl-Dieter Crisman]
Martin Albrecht
it seems
if [ -f /etc/issue ] && grep "Ubuntu 11.04" /etc/issue ; then
echo "Patching src/Modules/Setup.dist as this is Ubuntu 11.04"
patch -p0 < patches/Modules.Setup.dist.patch
if [ $? -ne 0 ]; then
echo "Error patching src/Modules/Setup.dist"
exit 1
fi
fi
from
http://trac.sagemath.org/sage_trac/ticket/11243
is not enough any more, since my build fails on a Debian/testing AMD64 machine
(cf. http://sage.math.washington.edu/home/malb/python-2.6.4.p10.log )
Forcing that patch to be applied makes the build go through. I'll report back
once the build finished (ATLAS doesn't know my i7 so it takes a while)
Cheers,
Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
_www: http://martinralbrecht.wordpress.com/
_jab: martinr...@jabber.ccc.de
leif
> Hi,
>
> it seems
>
> if [ -f /etc/issue ] && grep "Ubuntu 11.04" /etc/issue ; then
> echo "Patching src/Modules/Setup.dist as this is Ubuntu 11.04"
> patch -p0 < patches/Modules.Setup.dist.patch
> if [ $? -ne 0 ]; then
> echo "Error patching src/Modules/Setup.dist"
> exit 1
> fi
> fi
>
> from
>
> http://trac.sagemath.org/sage_trac/ticket/11243
>
> is not enough any more, since my build fails on a Debian/testing AMD64 machine
>
> (cf. http://sage.math.washington.edu/home/malb/python-2.6.4.p10.log )
>
> Forcing that patch to be applied makes the build go through.
Already known and fixed... :-)
See http://trac.sagemath.org/sage_trac/ticket/11447 (needs review btw)
and give
http://spkg-upload.googlecode.com/files/python-2.6.4.p11.spkg
a try. (md5sum: 5bc63c1814fc7ae34f4fed5a8fffe380)
Cheers,
-leif
> I'll report back
> once the build finished (ATLAS doesn't know my i7 so it takes a while)
>
> Cheers,
> Martin
>
> --
> name: Martin Albrecht
> _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
> _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
> _www: http://martinralbrecht.wordpress.com/
> _jab: martinr...@jabber.ccc.de
>
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML Email
leif
> Martin Albrecht wrote:
>> http://trac.sagemath.org/sage_trac/ticket/11243
>>
>> is not enough any more, since my build fails on a Debian/testing AMD64
>> machine
>> (cf. http://sage.math.washington.edu/home/malb/python-2.6.4.p10.log )
>>
>> Forcing that patch to be applied makes the build go through.
>
> Already known and fixed... :-)
>
> See http://trac.sagemath.org/sage_trac/ticket/11447 (needs review btw)
>
> and give
>
> http://spkg-upload.googlecode.com/files/python-2.6.4.p11.spkg
>
> a try. (md5sum: 5bc63c1814fc7ae34f4fed5a8fffe380)
P.S.: The above spkg requires the dpkg-dev package to be installed on
the affected Debian & derivative systems to make the fix effective.
We do not yet give a hint on that in case the crypt import test fails;
cf. http://trac.sagemath.org/sage_trac/ticket/11447#comment:23
-leif
Jeroen Demeyer
> Hi,
>
> it seems
>
> if [ -f /etc/issue ] && grep "Ubuntu 11.04" /etc/issue ; then
> echo "Patching src/Modules/Setup.dist as this is Ubuntu 11.04"
> patch -p0 < patches/Modules.Setup.dist.patch
> if [ $? -ne 0 ]; then
> echo "Error patching src/Modules/Setup.dist"
> exit 1
> fi
> fi
>
> from
>
> http://trac.sagemath.org/sage_trac/ticket/11243
That was an extremely bad solution to the problem, too bad I didn't
notice it before merging.
Volker Braun
Volker Braun
leif
=== Patches ===
[...]
* setup.py.multiarch.patch: Library search dir is expanded on Debian
and derivatives with multiarch (see #11243, #11447).
This requires 'dpkg-architecture' to be installed on the affected
systems.
(Since the patch origins from Python 2.7, it can certainly be removed
when we upgrade to that. But the patch then won't apply anymore anyway.)
;-)
Martin Albrecht
> leif wrote:
> > Martin Albrecht wrote:
> >> http://trac.sagemath.org/sage_trac/ticket/11243
> >>
> >> is not enough any more, since my build fails on a Debian/testing AMD64
> >> machine
> >> (cf. http://sage.math.washington.edu/home/malb/python-2.6.4.p10.log )
> >>
> >> Forcing that patch to be applied makes the build go through.
> >
> > Already known and fixed... :-)
> >
> > See http://trac.sagemath.org/sage_trac/ticket/11447 (needs review btw)
> >
> > and give
> >
> > http://spkg-upload.googlecode.com/files/python-2.6.4.p11.spkg
> >
> > a try. (md5sum: 5bc63c1814fc7ae34f4fed5a8fffe380)
Yep, that worked.
Rob Beezer
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
no repeat of the four known doctest failures for matrix groups).
Justin C. Walker
On Jul 4, 2011, at 05:00 , Jeroen Demeyer wrote:
> Dear Sage lovers,
>
> We're releasing Sage 4.7.1.alpha4.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.1.alpha4/sage-4.7.1.alpha4.tar
>
> Upgrade path:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.1.alpha4/sage-4.7.1.alpha4/
Built from scratch on Mac OS X, 10.6.8 (Dual 6-core Xeon), w/o problems. All tests ("ptestlong") passed!
Built as upgrade from 4.7.1-a2->4.7.1-a3, on Mac OS X, 10.6.8 (Core i7). Upgrade succeeded, and VERSION.txt was updated, but testing ("ptestlong") would not start, and, similarly, attempts to just run sage (as "./sage") yield with this error:
===============================================
----------------------------------------------------------------------
| Sage Version 4.7.1.alpha2, Release Date: 2011-06-07 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------
**********************************************************************
* *
* Warning: this is a prerelease version, and it may be unstable. *
* *
**********************************************************************
---------------------------------------------------------------------------
ImportError Traceback (most recent call last)
/Users/Sage/sage-4.7.1.alpha2/local/lib/python2.6/site-packages/IPython/ipmaker.pyc in force_import(modname)
64 reload(sys.modules[modname])
65 else:
---> 66 __import__(modname)
67
68
/Users/Sage/sage-4.7.1.alpha2/local/bin/ipy_profile_sage.py in <module>()
5 preparser(True)
6
----> 7 import sage.all_cmdline
8 sage.all_cmdline._init_cmdline(globals())
9
/Users/Sage/sage-4.7.1.alpha2/local/lib/python2.6/site-packages/sage/all_cmdline.py in <module>()
12 try:
13
---> 14 from sage.all import *
15 from sage.calculus.predefined import x
16 preparser(on=True)
/Users/Sage/sage-4.7.1.alpha2/local/lib/python2.6/site-packages/sage/all.py in <module>()
83
84 # This must come before Calculus -- it initializes the Pynac library.
---> 85 import sage.symbolic.pynac
86
87 from sage.modules.all import *
/Users/Sage/sage-4.7.1.alpha2/local/bin/expression.pxd in init sage.symbolic.pynac (sage/symbolic/pynac.cpp:19320)()
/Users/Sage/sage-4.7.1.alpha2/local/bin/getitem.pxd in init sage.symbolic.expression (sage/symbolic/expression.cpp:35259)()
ImportError: No module named getitem
Error importing ipy_profile_sage - perhaps you should run %upgrade?
WARNING: Loading of ipy_profile_sage failed.
===============================================
(I did get the "sage:" prompt, though).
VERSION.txt says:
===============================================
Sage version 4.7.1.alpha4, released 2011-07-03, updated from Sage version 4.7.1.alpha4, released 2011-07-03, updated from Sage version 4.7.1.alpha3, released 2011-06-24, updated from Sage version 4.7.1.alpha3, released 2011-06-24
===============================================
--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's income
-----------
--
They said it couldn't be done, but sometimes,
it doesn't work out that way.
- Casey Stengel
--
leif
> Built as upgrade from 4.7.1-a2->4.7.1-a3, on Mac OS X, 10.6.8 (Core i7). Upgrade succeeded, and VERSION.txt was updated, but testing ("ptestlong") would not start, and, similarly, attempts to just run sage (as "./sage") yield with this error:
>
> ===============================================
> ----------------------------------------------------------------------
> | Sage Version 4.7.1.alpha2, Release Date: 2011-06-07 |
> | Type notebook() for the GUI, and license() for information. |
> ----------------------------------------------------------------------
Well, the banner at least contains the wrong version number.
As far as I know, upgrading *from* alphas and rcs is -- unfortunately --
no longer supported, because meanwhile all alphas and rcs are created
"from scratch" relative to the most recent *final* version of Sage.
(The ".../local/bin/" prefix is a bit strange though.)
> VERSION.txt says:
>
> ===============================================
> Sage version 4.7.1.alpha4, released 2011-07-03, updated from Sage version 4.7.1.alpha4, released 2011-07-03, updated from Sage version 4.7.1.alpha3, released 2011-06-24, updated from Sage version 4.7.1.alpha3, released 2011-06-24
> ===============================================
That's quite funny (all versions upgraded to appearing twice).
I guess that's due to Sage attempting the upgrade twice, the second time
only to make sure that there's nothing left to upgrade, i.e., the first
attempt succeeded.
-leif
> They said it couldn't be done, but sometimes,
> it doesn't work out that way.
> - Casey Stengel
Agreed.
leif
> Justin C. Walker wrote:
>> VERSION.txt says:
>>
>> ===============================================
>> Sage version 4.7.1.alpha4, released 2011-07-03, updated from Sage
>> version 4.7.1.alpha4, released 2011-07-03, updated from Sage version
>> 4.7.1.alpha3, released 2011-06-24, updated from Sage version
>> 4.7.1.alpha3, released 2011-06-24
>> ===============================================
>
> That's quite funny (all versions upgraded to appearing twice).
>
> I guess that's due to Sage attempting the upgrade twice, the second time
> only to make sure that there's nothing left to upgrade, i.e., the first
> attempt succeeded.
Also, the original / first version, alpha2, is missing.
-leif
leif
[P.]P.S.:
Do you have SAGE_PATH set?
(If so,) Try
$ unset SAGE_PATH
and rerun 'make ptestlong' (or just try to start Sage).
This variable seems to currently have strange "side effects" :-) messing
up sys.path (the list of directories where Python modules get imported
from), especially [or only?] for modules imported from IPython's modules.
-leif
Justin C. Walker
On Jul 8, 2011, at 13:55 , leif wrote:
> Justin C. Walker wrote:
>> Built as upgrade from 4.7.1-a2->4.7.1-a3, on Mac OS X, 10.6.8 (Core i7). Upgrade succeeded, and VERSION.txt was updated, but testing ("ptestlong") would not start, and, similarly, attempts to just run sage (as "./sage") yield with this error:
>> ===============================================
>> ----------------------------------------------------------------------
>> | Sage Version 4.7.1.alpha2, Release Date: 2011-06-07 |
>> | Type notebook() for the GUI, and license() for information. |
>> ----------------------------------------------------------------------
>
> Well, the banner at least contains the wrong version number.
Yup. Not sure why.
[snip]
> As far as I know, upgrading *from* alphas and rcs is -- unfortunately -- no longer supported, because meanwhile all alphas and rcs are created "from scratch" relative to the most recent *final* version of Sage.
I know that, but it often does "work". I always build one pre-release from scratch and also attempt an upgrade (but not from a release).
> (The ".../local/bin/" prefix is a bit strange though.)
Why? All instances are in SAGE_ROOT, no?
>> VERSION.txt says:
>> ===============================================
>> Sage version 4.7.1.alpha4, released 2011-07-03, updated from Sage version 4.7.1.alpha4, released 2011-07-03, updated from Sage version 4.7.1.alpha3, released 2011-06-24, updated from Sage version 4.7.1.alpha3, released 2011-06-24
>> ===============================================
>
> That's quite funny (all versions upgraded to appearing twice).
>
> I guess that's due to Sage attempting the upgrade twice, the second time only to make sure that there's nothing left to upgrade, i.e., the first attempt succeeded.
As you say in a follow-on, -a2 is *not* mentioned (and the banner insists on -a2).
And to answer your latest query, SAGE_PATH is *not* set in my environment, and I don't see it after running "./sage -sh" and looking at "env" output.
Thanks for checking this stuff.
Justin
--
Justin C. Walker, Curmudgeon-at-Large
leif
> On Jul 8, 2011, at 13:55 , leif wrote:
>> (The ".../local/bin/" prefix is a bit strange though.)
>
> Why? All instances are in SAGE_ROOT, no?
Yes, but expression.pxd and getitem.pxd are not located in
$SAGE_ROOT/local/bin.
> And to answer your latest query, SAGE_PATH is *not* set in my environment, and I don't see it after running "./sage -sh" and looking at "env" output.
Hmmm... Just a guess, as this recently caused similar import errors when
running 'make ptestlong' and likewise './sage -tp ...' (but not 'make
testlong' or './sage -t ...').
(Haven't tracked this down yet, though I meanwhile can -- at least
partially -- reproduce it. This happened with a build from scratch btw.)
You *may* try running './sage -ba-force' to rebuild the whole Sage library.
-leif
--