Martin Raum wrote:
In #7928 due to the fact that the default python waring filter
displays warnings only once a comment on this behaviour is added and
that's it.
I would like to reinitiate a discussion on this, arguing that Sage
should define its own warning classes.
Use case for example:
I have
> andrejv wrote:
> > On Jan 10, 6:15 pm, Harald Schilly wrote:
> > > Hi, I got this from the report a problem link:
>
> > > Typing (in the inotebook)
>
> > > var('t,k,i')
> > > sum(binomial(i+t,t),i,0,k)
>
> > > results in
>
> > > binomial(k + t + 1, t + 1) - 1
>
> > > which is false, the well-kn
2010/1/16 Dima Pasechnik :
>
>
> On Jan 17, 12:53 pm, "Dr. David Kirkby"
> wrote:
>> Dima Pasechnik wrote:
>> > I understand that Debian support is on hold. AFAIK, a proper Debian
>> > requires a complete refactoring
>> > of the code, in particular removing all the things that are not really
>> >
On Jan 17, 12:53 pm, "Dr. David Kirkby"
wrote:
> Dima Pasechnik wrote:
> > I understand that Debian support is on hold. AFAIK, a proper Debian
> > requires a complete refactoring
> > of the code, in particular removing all the things that are not really
> > Sage, e.g. mercurial, gap, singular, e
2010/1/16 Dima Pasechnik :
> I understand that Debian support is on hold. AFAIK, a proper Debian
> requires a complete refactoring
> of the code, in particular removing all the things that are not really
> Sage, e.g. mercurial, gap, singular, etc etc etc.
> I understand it has been done at some poi
Dima Pasechnik wrote:
I understand that Debian support is on hold. AFAIK, a proper Debian
requires a complete refactoring
of the code, in particular removing all the things that are not really
Sage, e.g. mercurial, gap, singular, etc etc etc.
I understand it has been done at some point for Sage 3
I understand that Debian support is on hold. AFAIK, a proper Debian
requires a complete refactoring
of the code, in particular removing all the things that are not really
Sage, e.g. mercurial, gap, singular, etc etc etc.
I understand it has been done at some point for Sage 3, but then the
main pers
William Stein wrote:
What version were you upgrading from?
SAGE Version 3.1.2, Release Date: 2008-09-19
That's too old of a version of Sage. You will need to do a fresh install.
William
Ideally, it would be good if the 'upgrade' option has some sort of mechanism for
determining when an u
2010/1/16 Igor Tolkov :
> On Jan 16, 12:18 pm, William Stein wrote:
>> 2010/1/16 Igor Tolkov :
>>
>> > My SAGE upgrade (using sage --upgrade) on the machine:
>>
>> What GCC?
>
> Using built-in specs.
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
> 4.3.
On Jan 16, 12:18 pm, William Stein wrote:
> 2010/1/16 Igor Tolkov :
>
> > My SAGE upgrade (using sage --upgrade) on the machine:
>
> What GCC?
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
4.3.3-5ubuntu4' --with-bugurl=file:///usr/sh
2010/1/16 Igor Tolkov :
> My SAGE upgrade (using sage --upgrade) on the machine:
What GCC?
Precisely what computer?
What version were you upgrading from?
Post a link to the complete install.log file.
>
> Linux IT 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64
> GNU/Linux
>
> failed
My SAGE upgrade (using sage --upgrade) on the machine:
Linux IT 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64
GNU/Linux
failed with the following error:
g++ -o groebner/src/randomset.o -c -O3 -Wno-long-long -Wreturn-type -g
-fPIC -ftemplate-depth-100 -g -fPIC -O3 -Wno-long-long -W
Robert Miller wrote:
Greetings!
sage-4.3.1.rc0 is finally here. This should be a good base version for
Bug Days, and closes a good deal of tickets. I thought it would be
good to plan on an rc1 with just the ticket to fix building on OS X
10.6 (thoughts?). Also, reverting #7818 fixed a good deal
On Thu, Nov 05, 2009 at 09:47:30AM +1100, Alex Ghitza wrote:
>
>
> Hi Willem Jan, Ronald,
>
>
> I'm putting this on my todo list. About half a year ago I did some
> work adding doctests and fixing/reorganising things with scheme
> morphisms, but I didn't get a chance to finish. I'll try to ha
To some extent, these problems might go away if people used
nolabels:true in the files that they wrote to define their packages.
Then the the names that they leave around might be more likely to
be the names that they deliberately left around, and not the auto-
generated
names like C1, D1, %i1, %o2
Hi Robert,
On Mon, 11 Jan 2010 23:58:54 -0800 (PST)
"ma...@mendelu.cz" wrote:
> Dear sage-devel
>
> the following (definite) integral is not evaluated by maxima and show
> () command should return the same unevaluated integral in TeX
> notation. I think this was the case in previous versions. O
Hi Andrej,
On Mon, 11 Jan 2010 08:08:52 -0800 (PST)
andrejv wrote:
> On Jan 10, 6:15 pm, Harald Schilly wrote:
> > Hi, I got this from the report a problem link:
> >
> > Typing (in the inotebook)
> >
> > var('t,k,i')
> > sum(binomial(i+t,t),i,0,k)
> >
> > results in
> >
> > binomial(k + t + 1,
2010/1/16 John Cremona :
> 2010/1/16 William Stein :
>>>
>>> Should we open one ticket to fix all the errors?
>>
>> Yes, since doing otherwise will get confusing. If we have trouble
>> with this because of some particular issue, open a ticket for that
>> issue.
>>
>
> OK, it is now #7948. It sho
In which case you might read
http://www.edge.org/3rd_culture/lanier06/lanier06_index.html
A quote
Just as people are willing to bend over backwards and make themselves
stupid in order to make an AI interface appear smart (as happens when
someone can interact with the notorious Microsoft paper cl
2010/1/16 William Stein :
> On Sat, Jan 16, 2010 at 8:24 AM, John Cremona wrote:
>> When building 4.3.1.rc0 there were a lot (240 lines) of errors in
>> processing the documentation. We should surely fix these,
>>
>> Some I understand and know how to fix (e.g. unexpected indentation),
>> but what
On Sat, Jan 16, 2010 at 8:24 AM, John Cremona wrote:
> When building 4.3.1.rc0 there were a lot (240 lines) of errors in
> processing the documentation. We should surely fix these,
>
> Some I understand and know how to fix (e.g. unexpected indentation),
> but what are these about?
>
> /home/john/
On 16 led, 07:42, Robert Miller wrote:
> Greetings!
>
> sage-4.3.1.rc0 is finally here. This should be a good base version for
> Bug Days, and closes a good deal of tickets. I thought it would be
> good to plan on an rc1 with just the ticket to fix building on OS X
> 10.6 (thoughts?). Also, reve
http://trac.sagemath.org/sage_trac/ticket/7932
describes what is a quite serious problem with the Solaris build. Robert's
recent changes which add _Complex_I, are breaking the build on Solaris since
there is a bug in gcc on Solaris. A simple bit of code which compiles on Linux
with gcc, or Sol
Minh Nguyen wrote:
Hi folks,
It's that time of the year again when the copyright years for Sage
need to be updated to reflect the new year. The copyright years should
now span 2005--2010. The Sage wiki contains a page [1] that lists file
you need to edit in order to update the copyright years. S
Hi Vincent,
Sorry I didn't answer before I've been really busy.
Until know the LiveCD has been created from scratch and is based on Jaunty.
I created a custom base cd on which I work upon so even if I share with the
script with the community I won't make any sense. Besides you've got to
build
Sag
25 matches
Mail list logo
