sage-4.6.2.alpha3 released
Jeroen Demeyer
We're releasing Sage 4.6.2.alpha3.
Source archive:
http://sage.math.washington.edu/home/release/sage-4.6.2.alpha3/sage-4.6.2.alpha3.tar
Upgrade path:
http://sage.math.washington.edu/home/release/sage-4.6.2.alpha3/sage-4.6.2.alpha3/
Please build, test, and report! We'd love to hear about your
experiences with this release.
== Known issues ==
* Some doctests fail on bsd.math (OS X 10.6 i386), when compiling in
64-bit mode due to SAGE64 verbosity. This is #10303.
== Tickets ==
* We closed 176 tickets in this release. For details, see
http://sage.math.washington.edu/home/release/sage-4.6.2.alpha3/tickets.html
Merged in sage-4.6.2.alpha3:
#4492: Willem Jan Palenstijn: block_matrix reacts inconsistently with 0
[Reviewed by Aly Deines, Rob Beezer]
#7458: Carlo Hamalainen, Luis Felipe Tabera Alonso: Sylvester matrix for
polynomials [Reviewed by David Loeffler]
#7524: Karl-Dieter Crisman: frame axes are lost when saving a graphic to
a file [Reviewed by Andrey Novoseltsev]
#8442: Daniel Bump: Lie Methods and Related Combinatorics (tutorial)
[Reviewed by Minh Van Nguyen, Mark Jordan, Dmitrii Pasechnik]
#8456: Robert Bradshaw: lazy import improvements [Reviewed by Luis
Felipe Tabera Alonso]
#8948: Jason Grout, Rob Beezer: add thin space between vector entries
[Reviewed by Rob Beezer, Andrey Novoseltsev]
#9437: David Loeffler: special linear group over finite rings [Reviewed
by John Cremona]
#9599: Simon King, John Perry, Martin Albrecht: re-merge #1396 and
insure that Sage starts + passes doc tests on t2.math [Reviewed by
Martin Albrecht]
#9646: Chris Wuthrich: Incorrect calculation of elliptic curve formal
group law [Reviewed by David Loeffler]
#9791: Stefan Reiterer, Jeroen Demeyer: Fix documentation for weave in
the "numerical_sage" document [Reviewed by André Apitzsch]
#9918: Volker Braun: triangulate point configurations [Reviewed by
Marshall Hampton]
#9923: Nathann Cohen: Minimum Feedback Arc/Vertex set through constraint
generation [Reviewed by Robert Miller]
#10143: Karl-Dieter Crisman: Bring 2D plotting up to 100% doctest
coverage (except plot.py) [Reviewed by Minh Van Nguyen, Geoffrey Ehrman]
#10173: Willem Jan Palenstijn: asking if polynomial element in list
gives error [Reviewed by Geoffrey Ehrman]
#10222: Francis Clarke: Bernoulli polynomial problem [Reviewed by David
Loeffler]
#10251: Joris Vankerschaver: Bessel functions of real argument have
small imaginary component when scipy is used [Reviewed by Simon Spicer]
#10331: Martin Albrecht: degree of semi-regularity [Reviewed by Marshall
Hampton]
#10341: Martin Albrecht, Nathann Cohen: make MIP backend interface more
Python-ic [Reviewed by Martin Albrecht, Nathann Cohen]
#10432: Nathann Cohen: is_directed_acyclic is Cython (--> without
NetworX) and its certificates [Reviewed by Robert Miller]
#10435: Robert Miller: Invalid write in bitsets [Reviewed by Nathann Cohen]
#10449: André Apitzsch: DeprecationWarning for popen3 in ECM [Reviewed
by Robert Bradshaw]
#10450: David Loeffler: Problem computing Hecke matrices on subspaces of
modular forms spaces [Reviewed by Alex Ghitza]
#10454: Rob Beezer: Add .is_singular method to matrices [Reviewed by
Robert Bradshaw]
#10457: Marina Gresham, Aly Deines, Gagan Sekhon: Hyperelliptic curve
Cartier matrix and Hasse-Witt matrix [Reviewed by Aly Deines]
#10471: Rob Beezer: Add the conjugate-transpose of a matrix, by that
name [Reviewed by Robert Bradshaw]
#10500: Rob Beezer: Documentation clean-up for linear combinations of
matrix rows/columns [Reviewed by Aly Deines]
#10515: Christian Stump, Aly Deines: Removed bug in MatrixGroup.list()
[Reviewed by Gagan Sekhon]
#10526: Ryan Grout: plot option gridlines='minor' broken [Reviewed by
Geoff Ehrman, Marshall Hampton]
#10535: Rob Beezer, Jason Grout: A column-oriented matrix constructor
[Reviewed by Dan Drake]
#10537: Rob Beezer: Fix dictionary input to sparse vector constructor
[Reviewed by Dmitrii Pasechnik]
#10564: Jean-Pierre Flori: bug in symbolic sums [Reviewed by André Apitzsch]
#10578: Willem Jan Palenstijn: Coercion problem for vectors from
polynomial rings over GF(2) [Reviewed by Dmitrii Pasechnik]
#10579: Willem Jan Palenstijn: echelon_form docstring claims result not
cached [Reviewed by Aly Deines]
#10593: André Apitzsch: Replace __getslice__ with functionality in
__getitem__ in ContinuedFraction [Reviewed by Robert Bradshaw]
#10610: Willem Jan Palenstijn: tachyon block=False doesn't work
[Reviewed by Volker Braun]
#10626: Rob Beezer: Route sparse integer matrices to a working Smith
form [Reviewed by David Loeffler]
#10627: Ivan Andrus: add options for printing matrices [Reviewed by Rob
Beezer]
#10641: Johan Oudinet: fix documentation in
sage.misc.package.install_all_optional_packages [Reviewed by Gagan Sekhon]
#10644: Yann Ponty: examples in Common Graphs doc not interpreted
[Reviewed by Gagan Sekhon]
#10650: Robin Langer: documentation bug in the class
sage.calculus.riemann.ColorPlot [Reviewed by Gagan Sekhon]
#10681: Volker Braun: Tachyon on 32-bit OSX still sets CC=cc [Reviewed
by John Palmieri, Jeroen Demeyer]
#10686: Alex Ghitza: speed up computation of T_p in characteristic p
[Reviewed by David Loeffler]
#10695: Jeroen Demeyer: Use execv() instead of Subprocess.call() in
sage-run [Reviewed by Willem Jan Palenstijn]
#10697: Minh Van Nguyen: documentation bug in linear programming
tutorial [Reviewed by Robert Bradshaw]
Nathann Cohen
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To post to this group, send email to sage-r...@googlegroups.com.
To unsubscribe from this group, send email to sage-release...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sage-release?hl=en.
Volker Braun
Rob Beezer
$ make ptestlong
on 64-bit Ubuntu 10.04 on Intel Core Duo and (mobile) i7 passes all
tests.
I needed the one-line sage-update script hack to upgrade an existing
copy and get current.
http://groups.google.com/group/sage-release/msg/73d6d56be47344ab
Rob
Jeroen Demeyer
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on reference.log.
> make: *** [reference.pdf] Error 1
> Build finished. The built documents can be found in
> /dev/shm/mvngu/sage-4.6.2.alpha3/devel/sage/doc/output/pdf/en/reference
This happens since sage-4.6.2.alpha0.
I think the most serious issue here is that the build simply continues
after this error.
Justin C. Walker
On Jan 30, 2011, at 01:45 , Jeroen Demeyer wrote:
> Dear Sage lovers,
>
> We're releasing Sage 4.6.2.alpha3.
>
> Source archive:
>
> http://sage.math.washington.edu/home/release/sage-4.6.2.alpha3/sage-4.6.2.alpha3.tar
Built from scratch (Mac OS X, 10.6.6, Dual Quad Xeon) w/o problems.
Testing wouldn't even get started. The following was the first error:
ImportError: No module named base
from a sphinx-build (AFAICT).
The (bzipped) log file is attached. I assume I've done something dumb, but I'm currently in Clueless County...
Justin
Nathann Cohen
Sorry about that !!!!! Here is the result, though I do not understand
how it is related ^^;
/home/ncohen/sage$ LD_LIBRARY_PATH=./local/lib ldd
./devel/sage-main/c_lib/libcsage.so
linux-gate.so.1 => (0x00e61000)
libntl.so => ./local/lib/libntl.so (0x00110000)
libgmp.so.3 => ./local/lib/libgmp.so.3 (0x00605000)
libpari-gmp-2.4.so.3 => ./local/lib/libpari-gmp-2.4.so.3 (0xb751e000)
libpython2.6.so.1.0 => ./local/lib/libpython2.6.so.1.0 (0x00926000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x002d7000)
libm.so.6 => /lib/libm.so.6 (0x003c6000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00ebb000)
libc.so.6 => /lib/libc.so.6 (0x00b76000)
libpthread.so.0 => /lib/libpthread.so.0 (0x003f0000)
libdl.so.2 => /lib/libdl.so.2 (0x0040c000)
libutil.so.1 => /lib/libutil.so.1 (0x00574000)
/lib/ld-linux.so.2 (0x00586000)
Nathann
Volker Braun
Dr. David Kirkby
To the best of my knowledge, Sage *prepends* it's own LD_LIBRARY_PATH, so what
the user sets in advance should not make too much difference.
One thing to note, is that this should be set with either
LD_LIBRARY_PATH=/what/first/path:/what/second/path
export LD_LIBRARY_PATH
(This is preferable to the less portable:
export LD_LIBRARY_PATH=/what/first/path:/what/second/path
)
Just typing
LD_LIBRARY_PATH=/what/first/path:/what/second/path
will not work in most, (if any) shells.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Dave
Florent Hivert
For the record:
On Sun, Jan 30, 2011 at 10:45:47AM +0100, Jeroen Demeyer wrote:
> Dear Sage lovers,
>
> We're releasing Sage 4.6.2.alpha3.
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 1829.5 seconds
sur openSUSE 11.3 (x86_64)
Linux popcorn.rouba.net 2.6.34.7-0.7-desktop #1 SMP PREEMPT 2010-12-13 11:13:53 +0100 x86_64 x86_64 x86_64 GNU/Linux
Intel(R) Core(TM) i7 CPU X 920 @ 2.00GHz
8GB ram.
By the way
real 31m17.269s
The previous version (4.6.1) build took less than 30min.
Cheers,
Florent
Thomas Dziedzic
> Dear Sage lovers,
>
> We're releasing Sage 4.6.2.alpha3.
>
> Source archive:
>
>
> Upgrade path:
>
> http://sage.math.washington.edu/home/release/sage-4.6.2.alpha3/sage-4...
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
>
> == Known issues ==
>
> * Some doctests fail on bsd.math (OS X 10.6 i386), when compiling in
> 64-bit mode due to SAGE64 verbosity. This is #10303.
>
> == Tickets ==
>
> * We closed 176 tickets in this release. For details, see
>
make
make ptestlong
all tests pass!
Jeroen Demeyer
> OT1/cmr/m/n ....4>cmr12<17.28><20.74><24.88>cmr17
>
> l.493808 ...hmetic Subgroups of ${\rm SL}_2(\ZZ)$}
>
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on reference.log.
> make: *** [reference.pdf] Error 1
> Build finished. The built documents can be found in
> /dev/shm/mvngu/sage-4.6.2.alpha3/devel/sage/doc/output/pdf/en/reference
Thanks for the report. Fixed by #10721 (positive_review)
Concerning the building of documentation, it would be nice if somebody
could review #10351.
Jeroen.
Justin C. Walker
There is, in this response, essentially no context for your message.
There is a well-established "protocol" for email interaction on lists such as the Sage lists:
Include some (but usually not all) of the email you are replying to, including who sent it, and a little of the recent thread if it seems helpful to the discussion.
I'm not singling you out, Volker. There seems to be an increasing tendency to treat these threads (across most of the Sage lists!) as though they are just between two people (for whom the above might be overkill). Can we please keep this in mind when taking part in "email conversations"?
Finally: was your reply in response to my call for help with a "sphinx-build"?
Thanks, and apologies for the "preachy" flavor of my mail.
Justin
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To post to this group, send email to sage-r...@googlegroups.com.
> To unsubscribe from this group, send email to sage-release...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sage-release?hl=en.
>
--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
Like the ski resort full of girls hunting for husbands
and husbands hunting for girls, the situation is not
as symmetrical as it might seem.
- Alan MacKay
--
Franco Saliola
> Dear Sage lovers,
>
> We're releasing Sage 4.6.2.alpha3.
>
> Source archive:
>
> http://sage.math.washington.edu/home/release/sage-4.6.2.alpha3/sage-4.6.2.alpha3.tar
>
> Upgrade path:
>
> http://sage.math.washington.edu/home/release/sage-4.6.2.alpha3/sage-4.6.2.alpha3/
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
Build fails while *configuring* singular on Mac OS X 10.6.6:
configure: error: Unknown architecture: Check singuname.sh
Unable to configure Singular.
Here is my system information:
> uname -a
Darwin lacim-macpro-02.local 10.6.0 Darwin Kernel Version 10.6.0: Wed
Nov 10 18:11:58 PST 2010; root:xnu-1504.9.26~3/RELEASE_X86_64 x86_64
> uname -m
x86_64
The architecture detected by singular's configuration script
singuname.sh (located in
$SAGE_ROOT/spkg/build/singular-3-1-1-4.p3/src) spits out
x86_64-Unknown. Can someone with a similar machine---on which Sage
compiles---tell me their output of `uname -m`?
You can find the install log here:
http://thales.math.uqam.ca/~saliola/misc/install.log.bz2
Take care,
Franco
--
kcrisman
new-host-2:~ $ uname -m
i386
new-host-2:~ $ uname -a
Darwin new-host-2.home 10.6.0 Darwin Kernel Version 10.6.0: Wed Nov 10
18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386 i386
So maybe I'm not default-building in 64-bit mode (which is what the
x86_64 should indicate).
Did you try typing "make" again after the failure? Sometimes my
computer gets confused if I build using too many threads and I have to
do that.
- kcrisman
Franco Saliola
On Wed, Feb 2, 2011 at 1:54 PM, kcrisman <kcri...@gmail.com> wrote:
> Huh. That is interesting. I get
>
> new-host-2:~ $ uname -m
> i386
> new-host-2:~ $ uname -a
> Darwin new-host-2.home 10.6.0 Darwin Kernel Version 10.6.0: Wed Nov 10
> 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386 i386
>
> So maybe I'm not default-building in 64-bit mode (which is what the
> x86_64 should indicate).
>
> Did you try typing "make" again after the failure? Sometimes my
> computer gets confused if I build using too many threads and I have to
> do that.
Thanks for your response. I have tried this (several times, actually).
It seems that the Singular configuration scripts can't handle the
x86_64 output.
Obviously people here have successfully compiled Sage on this type of
machine, so I am confused about why this doesn't work for me.
Take care,
Franco
--
Rob Beezer
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
Ubuntu 10.10 on Intel i7-2600.
Volker Braun
Franco Saliola
On Thu, Feb 3, 2011 at 9:06 AM, Volker Braun <vbrau...@gmail.com> wrote:
> Considering that Singular 3.1.2 is out, can you check whether that
> version's singuname.sh works any better?
Thanks for the suggestion. I downloaded the latest source for Singular
(3.1.2.1) and ran singuname.sh and got the same output.
I also tried to follow the included installation instructions to
compile Singular from source, but I got stuck at step 6, which reads:
- fix ./singuname.sh not to report something unknown, but to recognize
the machine
Too funny! Any suggestions on what singuname.sh should report for this
machine? I'll post the output of uname below.
Franco
--
$ uname -a
Darwin lacim-macpro-02.local 10.6.0 Darwin Kernel Version 10.6.0: Wed
Nov 10 18:11:58 PST 2010; root:xnu-1504.9.26~3/RELEASE_X86_64 x86_64
$ uname -m
x86_64
--
Volker Braun
Franco Saliola
That seems to have worked. I unpacked the singular spkg, modified
singuname.sh to output what you suggested, re-packed the spkg, then I
ran make again. It seems to have built fine.
I ran make ptest and then make ptestlong. Are there other test suites
that I should run?
make ptestlong uncovered one problem:
----------------------------------------------------------------------
The following tests failed:
sage -t -long -force_lib
devel/sage/doc/en/bordeaux_2008/introduction.rst # 1 doctests failed
----------------------------------------------------------------------
But that test passed when I ran it on its own. Here is the error message:
OSError: [Errno 17] File exists:
'/Users/saliola/.sage//matplotlib-1.0.1/tex.cache'
so it was probably an artifact of parallel testing.
For the record, I asked about this on the singular forum earlier this afternoon:
http://www.singular.uni-kl.de/forum/viewtopic.php?f=10&t=1905
Take care,
Franco
--
Volker Braun
kcrisman
timeout.
- kcrisman