Dear Daniel,
I was glad that you and Nicolas wrote the combinatorial classes notes
last April. However, there wasn't any followup, so I wanted to check
if the situation has changed at all since then. I recently got an
email asking about my covering designs code, in which I had
Hi folks,
Below is a release note for Sage 4.3.1, compiled with the help of Mike
Hansen's script [1]. In this release, the lowest ticket number winner
is #383, which is closed thanks to Robert Bradshaw and William Stein.
Sage 4.3.1 was released on January 20th, 2010. It is available at
Hi!
In the last couple of days I am on a bug hunt, so far without the
faintest success. Perhaps you can help me with a Jedi mind intuition?
It is about the next (not yet released) version of my cohomology spkg.
If I compute the mod-2 cohomology ring of a certain non prime power
group, it works
I was a little disappointed that 4.3.1 was released, when I'd made it quite
clear there was a *new* problem, introduced since 4.3, which was causing the
build on Solaris SPARC to fail, despite earlier versions working on SPARC.
http://trac.sagemath.org/sage_trac/ticket/7990
(I marked it as a
Minh Nguyen wrote:
Hi Dan,
On Thu, Jan 21, 2010 at 3:26 PM, bump b...@match.stanford.edu wrote:
I had errors building sage-4.3.1.
Note this output from a configuration script (it's from the install
log you posted):
checking for g77... no
checking for xlf... no
checking for f77... no
On Thursday 21 January 2010, David Joyner wrote:
I have run some of these tests on an imac running 10.6.2
in sage 4.3.1 (sage-4.3.1.a5, to be precise) and
got what seems to be much shorter times
(see below). I'm not sure but it seems that at least for the
coding theory modules, there does not
On Thu, 21 Jan 2010 12:08:09 +, Dr. David Kirkby
david.kir...@onetel.net wrote:
Though it would appear the log posted by Dan
http://sporadic.stanford.edu/bump/sage-4.3.1-errors
shows the compiler was configured with Fortran support:
Configured with: ../src/configure -v
Alex Ghitza wrote:
On Thu, 21 Jan 2010 12:08:09 +, Dr. David Kirkby
david.kir...@onetel.net wrote:
Though it would appear the log posted by Dan
http://sporadic.stanford.edu/bump/sage-4.3.1-errors
shows the compiler was configured with Fortran support:
Configured with: ../src/configure
2010/1/21 Dr. David Kirkby david.kir...@onetel.net:
Alex Ghitza wrote:
On Thu, 21 Jan 2010 12:08:09 +, Dr. David Kirkby
david.kir...@onetel.net wrote:
Though it would appear the log posted by Dan
http://sporadic.stanford.edu/bump/sage-4.3.1-errors
shows the compiler was configured
However, the error message was fairly clear as to what needs to be done:
Error installing Fortran: You must install gfortran or set
SAGE_FORTRAN (and possibly SAGE_FORTRAN_LIB).
Yes, after installing gfortran I was able to build Sage.
Dan
--
To post to this group, send an email to
On Thu, Jan 21, 2010 at 3:22 AM, Pat LeSmithe qed...@gmail.com wrote:
Should we put
# -*- coding: utf-8 -*-
at the top of all .py and .pyx(?) files in the Sage library?
I think this will allow us to use Unicode literal strings in Sage code,
doctests, documentation --- without raising
John Cremona wrote:
I think this is one further example of the point I made less than an hour
ago. The removal of the Fortran package was made in sage-4.3.1.rc2, which
very quickly becomes 4.3.1, with insufficient time given for testing before
making the 4.3.1 release.
I agree -- this is
Not everyone can easily use a text editor which recognizes all non-
ASCII character properly, so I think we should be careful about
this.
- kcrisman
On Jan 21, 9:09 am, Gonzalo Tornaria torna...@math.utexas.edu wrote:
On Thu, Jan 21, 2010 at 3:22 AM, Pat LeSmithe qed...@gmail.com wrote:
On Thu, Jan 21, 2010 at 7:20 AM, Martin Albrecht
m...@informatik.uni-bremen.de wrote:
On Thursday 21 January 2010, David Joyner wrote:
I have run some of these tests on an imac running 10.6.2
in sage 4.3.1 (sage-4.3.1.a5, to be precise) and
got what seems to be much shorter times
(see below).
On Wed, Jan 20, 2010 at 5:47 PM, Peter Jeremy peterjer...@acm.org wrote:
My personal feeling is that it would be nice if some of the more generic
packages (eg bzip, zlib, readline, mercurial) were moved out of sage
and made explicit requirements.
+1
I think Sage is mature enough now to slowly
On Thu, Jan 21, 2010 at 12:16 PM, kcrisman kcris...@gmail.com wrote:
Not everyone can easily use a text editor which recognizes all non-
ASCII character properly, so I think we should be careful about
this.
I don't think that's true anymore. It may have been true ten years
ago, but nowadays
On Thu, Jan 21, 2010 at 6:09 AM, Gonzalo Tornaria
torna...@math.utexas.edu wrote:
On Thu, Jan 21, 2010 at 3:22 AM, Pat LeSmithe qed...@gmail.com wrote:
Should we put
# -*- coding: utf-8 -*-
at the top of all .py and .pyx(?) files in the Sage library?
I think this will allow us to use
Hi folks,
The release tour for Sage 4.3.1 [1] is nearly complete. If you can
help out with showcasing new features in Sage 4.3.1 in the release
tour, please do so. In case I missed some new features, I appreciate
your help in showcasing those new features. It would be good to have a
second pair
On Jan 21, 11:53 am, Dr. David Kirkby david.kir...@onetel.net
wrote:
I was a little disappointed that 4.3.1 was released, when I'd made it quite
clear there was a *new* problem, introduced since 4.3, which was causing the
build on Solaris SPARC to fail, despite earlier versions working on
On Thu, Jan 21, 2010 at 4:20 AM, Martin Albrecht
m...@informatik.uni-bremen.de wrote:
On Thursday 21 January 2010, David Joyner wrote:
I have run some of these tests on an imac running 10.6.2
in sage 4.3.1 (sage-4.3.1.a5, to be precise) and
got what seems to be much shorter times
(see below).
On Thu, Jan 21, 2010 at 7:09 AM, Bill Hart goodwillh...@googlemail.com wrote:
On Jan 21, 11:53 am, Dr. David Kirkby david.kir...@onetel.net
wrote:
I was a little disappointed that 4.3.1 was released, when I'd made it quite
clear there was a *new* problem, introduced since 4.3, which was
I think #7729 implementing Iwahori Hecke algebras deserves comment.
Dan
On Jan 21, 7:02 am, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi folks,
The release tour for Sage 4.3.1 [1] is nearly complete. If you can
help out with showcasing new features in Sage 4.3.1 in the release
tour, please
I would like to encourage people to review ticket 7109:
http://trac.sagemath.org/sage_trac/ticket/7109
This was originally submitted by Volker Braun, and I think it is his
first contribution to Sage. It is an important refactoring of the
polyhedra code in geometry/polyhedra.py. This rewrite is
On Thu, Jan 21, 2010 at 7:32 AM, mhampton hampto...@gmail.com wrote:
I would like to encourage people to review ticket 7109:
http://trac.sagemath.org/sage_trac/ticket/7109
This was originally submitted by Volker Braun, and I think it is his
first contribution to Sage. It is an important
Ah, I see. I missed the scroll bar at the bottom. Even so it's a real
fiddle to see which line is the problem.
It appears to be complaining about a system include file which is
supposed to test for features available on the system.
Never seen that before, and I don't think it is FLINT after all.
Hi folks,
I have setup a wiki page [1] to record the building and doctesting
results of Sage 4.3.1 on various platform/hardware combinations. Feel
free to add more results to that page.
[1] http://wiki.sagemath.org/devel/BuildFarm/sage-4.3.1
--
Regards
Minh Van Nguyen
--
To post to this
On Wed, Jan 20, 2010 at 02:02:05PM -0800, Jason Grout wrote:
William Stein wrote:
I argue for keeping the current design when I'm *doing* math.
I argue for changing echelon_form to return something over the
fraction field when I'm teaching undergraduates.
+1
Luckily enough, in France, the
I am less unhappy now, having managed to install gfortran. (There was
something broken in our ubuntu package management system, but I
managed to fix it luckily).
John
2010/1/21 Dr. David Kirkby david.kir...@onetel.net:
John Cremona wrote:
I think this is one further example of the point I
Hi,
WARNING: On Linux, if you do sage -upgrade right now, you may need to do
./sage -f numpy-1.3.0.p2.spkg scipy_sandbox-20071020.p4.spkg scipy-0.7.p3.spkg
(or something very similar) to force rebuild of some code that depends
on fortran libraries.
See
The OpenSolaris development repository seems to have a release cycle
of two weeks, but they have a source release or build which is made
available for internal testing (and whoever wants to test it badly
enough to build and install it themselves) roughly two weeks before
each release. From a user
Bill Hart wrote:
On Jan 21, 11:53 am, Dr. David Kirkby david.kir...@onetel.net
wrote:
I was a little disappointed that 4.3.1 was released, when I'd made it quite
clear there was a *new* problem, introduced since 4.3, which was causing the
build on Solaris SPARC to fail, despite earlier
On Thu, Jan 21, 2010 at 8:22 AM, brandon.bar...@gmail.com
brandon.bar...@gmail.com wrote:
The OpenSolaris development repository seems to have a release cycle
of two weeks, but they have a source release or build which is made
available for internal testing (and whoever wants to test it badly
On Wed, Jan 20, 2010 at 8:26 PM, bump b...@match.stanford.edu wrote:
I had errors building sage-4.3.1.
The trouble came after this warning:
sage-spkg fortran-20100118 21
Warning: Attempted to overwrite SAGE_ROOT environment variable
fortran-20100118
Eventually I got:
Error installing
On Tue, Jan 19, 2010 at 01:54:57PM -0800, Robert Miller wrote:
It's time to point our fingers at long doctests again. (I won't name
names, but there are a few people who are mostly responsible for
several of these files) Here are the eight files whose doctests
(without -long) take the longest:
Is there any reason why my password for logging into the wiki has
stopped working?
John
2010/1/21 bump b...@match.stanford.edu:
I think #7729 implementing Iwahori Hecke algebras deserves comment.
Dan
On Jan 21, 7:02 am, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi folks,
The release tour
On Thu, Jan 21, 2010 at 9:02 AM, John Cremona john.crem...@gmail.com wrote:
Is there any reason why my password for logging into the wiki has
stopped working?
I can't think of any. Mine still works. Maybe you forgot it?
John
2010/1/21 bump b...@match.stanford.edu:
I think #7729
William wrote:
It's possible he didn't set the DOT_SAGE environment variable to
something in /scratch, which will impact timings hugely (at least
until somebody rewrites Sage temp file code in misc/misc.py to use the
standard tempfile module).
DOT_SAGE was set to /scratch/rlm/.sage when I ran
2010/1/21 William Stein wst...@gmail.com:
On Thu, Jan 21, 2010 at 9:02 AM, John Cremona john.crem...@gmail.com wrote:
Is there any reason why my password for logging into the wiki has
stopped working?
I can't think of any. Mine still works. Maybe you forgot it?
I certainly had! but
On Thu, Jan 21, 2010 at 9:10 AM, Robert Miller r...@rlmiller.org wrote:
William wrote:
It's possible he didn't set the DOT_SAGE environment variable to
something in /scratch, which will impact timings hugely (at least
until somebody rewrites Sage temp file code in misc/misc.py to use the
William Stein wrote:
On Thu, Jan 21, 2010 at 8:22 AM, brandon.bar...@gmail.com
brandon.bar...@gmail.com wrote:
The OpenSolaris development repository seems to have a release cycle
of two weeks, but they have a source release or build which is made
available for internal testing (and whoever
OK, I added a referee patch.
-Marshall
On Jan 21, 9:38 am, William Stein wst...@gmail.com wrote:
On Thu, Jan 21, 2010 at 7:32 AM, mhampton hampto...@gmail.com wrote:
I would like to encourage people to review ticket 7109:
http://trac.sagemath.org/sage_trac/ticket/7109
This was originally
On Thu, Jan 21, 2010 at 5:21 PM, William Stein wst...@gmail.com wrote:
Hi,
WARNING: On Linux, if you do sage -upgrade right now, you may need to do
./sage -f numpy-1.3.0.p2.spkg scipy_sandbox-20071020.p4.spkg
scipy-0.7.p3.spkg
(or something very similar) to force rebuild of some code
On Thu, Jan 21, 2010 at 9:20 AM, William Stein wst...@gmail.com wrote:
If the problem really is the filesystem, then maybe /scratch is way
too slow. Can you try setting DOT_SAGE to something in /tmp or
/space, since /tmp could be far better than /scratch for large numbers
of accesses.
I just
Well then perhaps we should have a -very_long flag! I would think
that some very long doctests stress-test things in a way that may be
impossible with shorter tests - large memory usage for example.
-Marshall
On Jan 21, 1:03 pm, Robert Miller r...@rlmiller.org wrote:
On Thu, Jan 21, 2010 at
On Jan 21, 2010, at 8:37 AM, Dr. David Kirkby wrote:
It looks like the exact same version of FLINT, which did work in Sage
4.3, no longer works in 4.3.1. I can't imagine what the problem is.
(Guess: too much fiddling with the Sage build system.)
There's also no patch to fix the issue
On Thu, Jan 21, 2010 at 11:29 AM, mhampton hampto...@gmail.com wrote:
Well then perhaps we should have a -very_long flag! I would think
that some very long doctests stress-test things in a way that may be
impossible with shorter tests - large memory usage for example.
-Marshall
+1!
--
On Jan 21, 2010, at 6:31 AM, Gonzalo Tornaria wrote:
On Wed, Jan 20, 2010 at 5:47 PM, Peter Jeremy peterjer...@acm.org
wrote:
My personal feeling is that it would be nice if some of the more
generic
packages (eg bzip, zlib, readline, mercurial) were moved out of sage
and made explicit
Hi,
The new graph editor in sage by Rado is AWESOME. One can try it
easily at http://sagenb.org by typing:
g = graphs.CompleteGraph(10)
graph_editor(g)
The actual source code is at
local/lib/python/site-packages/sagenb-0.6-py2.6.egg/sagenb/data/graph_editor/
It would be *GREAT* if
I agree that it's awesome. I'm not sure if I'm using it right though. If I
remove a vertex from Williams example below, and then click Save, it changes
the cell, but the graph that it then creates is the same as before I removed
the vertex. The same problem seems to occur for most changes I
On Jan 21, 3:22 pm, William Stein wst...@gmail.com wrote:
Hi,
The new graph editor in sage by Rado is AWESOME. One can try it
+1 ! We had a lot of fun showing it off to people at the Joint
Meetings.
- kcrisman
--
To post to this group, send an email to sage-devel@googlegroups.com
To
Glad you liked it. I will write up the README in the next few days.
The spring layout definitely can be improved as I put in the first
thing that came to mind, but I know those things have been studied and
there are advanced algorithms. Eventually the sliders can be removed
if the algorithm is
On Thu, Jan 21, 2010 at 12:05 PM, Robert Bradshaw
rober...@math.washington.edu wrote:
On Jan 21, 2010, at 6:31 AM, Gonzalo Tornaria wrote:
On Wed, Jan 20, 2010 at 5:47 PM, Peter Jeremy peterjer...@acm.org wrote:
My personal feeling is that it would be nice if some of the more generic
Issues with the install:
README.txt needs updating. At least for Ubuntu ranlib doesn't show up as an
option for apt-get, but it is part of the binutils package. Also needs to be
updated re: the new requirements for gfortran. It still lists the old info.
GCC needs to be all lowercase for apt-get
On Thu, Jan 21, 2010 at 1:15 PM, Erik Lane erikl...@gmail.com wrote:
Issues with the install:
README.txt needs updating. At least for Ubuntu ranlib doesn't show up as an
option for apt-get, but it is part of the binutils package. Also needs to be
updated re: the new requirements for gfortran.
Hi Erik,
On Fri, Jan 22, 2010 at 8:15 AM, Erik Lane erikl...@gmail.com wrote:
Issues with the install:
README.txt needs updating. At least for Ubuntu ranlib doesn't show up as an
option for apt-get, but it is part of the binutils package. Also needs to be
updated re: the new requirements for
On Wed, Jan 20, 2010 at 10:06 PM, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi Robert,
On Thu, Jan 21, 2010 at 6:38 AM, Robert Bradshaw
rober...@math.washington.edu wrote:
SNIP
The single bad account can be deleted.
Now there is another spammer account with the username Robert. The
Hi David,
I couldn't reproduce that bug. One thing comes to mind is to note what
is written in the box variable name. The js editor and Sage
communicate only when you hit save and all that happens in that the
graph in the editor is saved under the name in variable name box.
When you say Save
It seemed to be only associated to that cell: if I took the generated code,
copied it into another cell and then made changes in the other cell, the
changes saved correctly.
I tried publishing the worksheet, but that seemed to change the state of the
cell sufficiently so that I can no longer
On 01/21/2010 12:22 PM, William Stein wrote:
local/lib/python/site-packages/sagenb-0.6-py2.6.egg/sagenb/data/graph_editor/
It would be *GREAT* if there were a README.txt file in that directory
that explained what all the js files actually are, something about how
the graph editor works,
On 21 Gen, 00:22, William Stein wst...@gmail.com wrote:
On Wed, Jan 20, 2010 at 1:33 PM, Maurizio maurizio.gran...@gmail.com wrote:
Hi all,
even if in the recent times I've been much less involved with SAGE, I
just wanted to point out two pieces of software that I hope could
become
On Thu, Jan 21, 2010 at 2:14 PM, Pat LeSmithe qed...@gmail.com wrote:
On 01/21/2010 12:22 PM, William Stein wrote:
local/lib/python/site-packages/sagenb-0.6-py2.6.egg/sagenb/data/graph_editor/
It would be *GREAT* if there were a README.txt file in that directory
that explained what all
I'll look over the referee patch.
Andrey
On Jan 21, 10:50 am, mhampton hampto...@gmail.com wrote:
OK, I added a referee patch.
-Marshall
On Jan 21, 9:38 am, William Stein wst...@gmail.com wrote:
On Thu, Jan 21, 2010 at 7:32 AM, mhampton hampto...@gmail.com wrote:
I would like to
On Thu, Jan 21, 2010 at 1:31 PM, William Stein wst...@gmail.com wrote:
On Thu, Jan 21, 2010 at 1:15 PM, Erik Lane erikl...@gmail.com wrote:
Issues with the install:
README.txt needs updating. At least for Ubuntu ranlib doesn't show up as
an
option for apt-get, but it is part of the
On Thu, Jan 21, 2010 at 1:41 PM, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi Erik,
On Fri, Jan 22, 2010 at 8:15 AM, Erik Lane erikl...@gmail.com wrote:
Issues with the install:
README.txt needs updating. At least for Ubuntu ranlib doesn't show up as
an
option for apt-get, but it is
Post it where? Here to the list? Should I assume that what holds true for
Ubuntu is more general, or just make notes in the text that let people know
that on Ubuntu that's the way it is? (Because that's all I have available to
me.)
I looked into it, and looks like it's very standard that
On Thu, Jan 21, 2010 at 01:31:26PM -0800, William Stein wrote:
We've hand-inspected the R failures and they are all because of
missing optional R packages that we don't include with Sage.
I also found out later that there's a new R spkg by kcrisman at #6532 (needs
review) that should pass all
Great, thanks!
I just realized I didn't do my referee patch correctly, but I just
added a new one that I think is correct.
-Marshall
On Jan 21, 4:58 pm, Andrey Novoseltsev novos...@gmail.com wrote:
I'll look over the referee patch.
Andrey
On Jan 21, 10:50 am, mhampton hampto...@gmail.com
Robert Bradshaw wrote:
On Jan 21, 2010, at 8:37 AM, Dr. David Kirkby wrote:
Having worked quite hard on the SPARC build, I was less than keen to
see it broken.
Yes, that is disappointing. I spent a fair amount of time trying to
resolve the first Solaris stopper that came up, but who knows
On Thu, Jan 21, 2010 at 4:22 PM, Pat LeSmithe qed...@gmail.com wrote:
Should we put
# -*- coding: utf-8 -*-
at the top of all .py and .pyx(?) files in the Sage library?
I think this will allow us to use Unicode literal strings in Sage code,
doctests, documentation --- without raising
On Fri, Jan 22, 2010 at 12:46 AM, Minh Nguyen nguyenmi...@gmail.com wrote:
With or without the above Unicode preamble, a non-ASCII character in a
docstring can cause the PDF version of a document to fail to build.
See ticket #8036 [1] for an example of a case where a source file
contains the
On Thu, Jan 21, 2010 at 6:05 PM, Robert Bradshaw
rober...@math.washington.edu wrote:
On Jan 21, 2010, at 6:31 AM, Gonzalo Tornaria wrote:
On Wed, Jan 20, 2010 at 5:47 PM, Peter Jeremy peterjer...@acm.org wrote:
My personal feeling is that it would be nice if some of the more generic
packages
On Thu, Jan 21, 2010 at 7:11 PM, William Stein wst...@gmail.com wrote:
+1 to Robert's comments. I can't tell you how many people just in the
last few days have told me that they use (and work on!) Sage *only*
because when they try to build it on their computer it just worked.
Do people tell
Gonzalo Tornaria wrote:
Plus, there can *still* be spkgs for all the dependencies. And there
could be a sage-with-batteries-included tarball which works just as
it does now. And another
sage-reduced-for-expert-developers-and-distros tarball which doesn't
include the spkgs which can be replaced
On Thu, Jan 21, 2010 at 8:09 PM, Gonzalo Tornaria
torna...@math.utexas.edu wrote:
I think Sage is mature enough now to slowly migrate toward this.
Besides, there can still be spkgs for those packages, and there could
be a sage-with-batteries-included tarball with dependencies included.
What
On Fri, Jan 22, 2010 at 3:24 AM, Dr. David Kirkby
david.kir...@onetel.net wrote:
But sorting out whether the version of libraries on a system are suitable,
can be tricky. Even having the right versions does not guarantee they will
be found in preference to some other version.
Sure. We already
On Fri, 22 Jan 2010 19:27:56 Gonzalo Tornaria wrote:
If you are only going to shave off 20 MB or so from the source code, it
might be more hassle than it is worth. If you could cut the download time
by 30%, then I could see it would probably be worth the effort in doing
this. But I'm not
Gonzalo Tornaria wrote:
On Fri, Jan 22, 2010 at 3:24 AM, Dr. David Kirkby
david.kir...@onetel.net wrote:
But sorting out whether the version of libraries on a system are suitable,
can be tricky. Even having the right versions does not guarantee they will
be found in preference to some other
On Thu, Jan 21, 2010 at 10:41 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
Gonzalo Tornaria wrote:
On Fri, Jan 22, 2010 at 3:24 AM, Dr. David Kirkby
david.kir...@onetel.net wrote:
But sorting out whether the version of libraries on a system are
suitable,
can be tricky. Even having
I'm going to update the 'prereq' script to add a test for a Fortran compiler. I
would like to know what we need.
This is what is a quick summary of what is currently tested in 'prereq'. Is
there anything else which should be added to this list.
1) Non GNU compilers permitted, but you need to
79 matches
Mail list logo
