Maybe I should try and build from source then. How do I uninstall the
version I have now, is it enough to just drag the Applications/sage folder
into the trash?
/Oskar
On Wednesday, May 7, 2014 11:24:01 AM UTC+2, Oskar Till wrote:
Just as I got my sage to work with topcom on my old laptop, I
On 9/05/2014, at 2005, Oskar Till oskar.e.t...@gmail.com wrote:
Maybe I should try and build from source then. How do I uninstall the version
I have now, is it enough to just drag the Applications/sage folder into the
trash?
Yes.
--
You received this message because you are subscribed to
Hi,
Le 06/05/2014 19:39, Jeroen Demeyer a écrit :
On 2014-05-06 16:53, John Cremona wrote:
In practice, it may be hard to gather the informatino on how much RAM
tests take
You could run them under ulimit -v and see when they start to fail.
But personally, I don't consider RAM usage by
On 2014-05-09 10:55, Julien Puydt wrote:
But personally, I don't consider RAM usage by doctests an issue.
Perhaps because you don't use old or limited computers?
No, because I think that doctest coverage is more important than memory
usage of doctests. It is perfectly possible to *use* Sage
Anne Schilling wrote:
We actually added tests for our k-Schur function book. But a lot of
time, when syntax in
Sage changes, these tests just get replaced by others without checking
with the authors
of the book/paper.
git log src/sage/tests/book_schilling_zabrocki_kschur_primer.py | grep
Well, testing, for instance, if everything runs in an ARM machine can be
painful. And if we want to deliver ARM binaries, we need to test everything
there.
El viernes, 9 de mayo de 2014 13:04:20 UTC+2, Jeroen Demeyer escribió:
On 2014-05-09 10:55, Julien Puydt wrote:
But personally, I
On 2014-05-09 13:41, mmarco wrote:
And if we want to deliver ARM binaries, we need to test
everything there.
This does not have to be the case. In fact, at some point we had Solaris
and OS X PPC binaries even though not everything was working 100% on
those platforms.
If there are a few files
We do have a arm machine in Oxford with more than enough ram (afair 4GB).
Dima did some work on finishing the arm port. In any case, its not a ram
issue.
On Friday, May 9, 2014 1:41:44 PM UTC+2, mmarco wrote:
Well, testing, for instance, if everything runs in an ARM machine can be
On Friday, May 9, 2014 1:40:51 PM UTC+2, leif wrote:
Probably each relevant file should contain a CAPSLOCK header with
information on how to contact the author(s) etc.
DEAR SIR WE HAVE RECENTLY COME INTO POSSESSION OF THIS EXTREMELY VALUABLE
DOCTEST FOR WHICH WE WOULD LIKE TO ENLIST YOUR
It's happened a few times that people have put tests in the sage/tests
directory which explicitly require that certain inputs return
NotImplementedError, or something similar. Surely we shouldn't have to
go through the rigmarole of contacting the original author and waiting
a year in order to add
Jeroen Demeyer wrote:
On 2014-05-09 10:55, Julien Puydt wrote:
But personally, I don't consider RAM usage by doctests an issue.
Perhaps because you don't use old or limited computers?
No, because I think that doctest coverage is more important than memory
usage of doctests. It is perfectly
On 2014-05-09 14:08, leif wrote:
And probably some build- or patchbots should run the tests with 'ulimit
-v $SAGE_DOCTEST_MEMORY_CUTOFF' by default.
Totally +1.
I always did that with a limit of 2.5GB.
--
You received this message because you are subscribed to the Google Groups
sage-devel
On 2014-05-09 14:08, David Loeffler wrote:
It's happened a few times that people have put tests in the sage/tests
directory which explicitly require that certain inputs return
NotImplementedError, or something similar. Surely we shouldn't have to
go through the rigmarole of contacting the
On 5/7/14, 0:41, Ivan Andrus wrote:
On May 6, 2014, at 11:47 AM, Jason Grout jason-s...@creativetrax.com wrote:
On 5/5/14, 14:20, Daniel Bell wrote:
Hi
I am one of the students who was selected for working with Sage for
Google Summer of Code. I will be working on the iOS app. One of the
On 8 May 2014 20:39, leif not.rea...@online.de wrote:
John Cremona wrote:
On 8 May 2014 09:30, Jeroen Demeyer jdeme...@cage.ugent.be
mailto:jdeme...@cage.ugent.be wrote:
If I'm not mistaken, the problem of writing N as a^2 + b^2 is
equivalent to finding a square root of -1 modulo
David Loeffler wrote:
It's happened a few times that people have put tests in the sage/tests
directory which explicitly require that certain inputs return
NotImplementedError, or something similar. Surely we shouldn't have to
go through the rigmarole of contacting the original author and waiting
Jeroen Demeyer wrote:
On 2014-05-09 14:08, David Loeffler wrote:
It's happened a few times that people have put tests in the sage/tests
directory which explicitly require that certain inputs return
NotImplementedError, or something similar. Surely we shouldn't have to
go through the rigmarole
leif wrote:
Should we put up signs telling people not to use the MacOS X pre-built
binaries (or the MacOS X app) with Xcode versions = 5.x?
Apparently the deployment targets currently compiled into Sage's GCC (on
the MacOS X buildslave[s]) don't work with more recent versions of Xcode
(5.x? or
Hello sage-dev,
While working on something else, I found out that although there is a
doctest that unpickles all objects in the pickle jar, it does not do any
kind of sanity check on the resulting objects. This means that unpickling
many of these objects has become completely broken over
On 2014-05-09, Volker Braun vbraun.n...@gmail.com wrote:
We do have a arm machine in Oxford with more than enough ram (afair 4GB).
Dima did some work on finishing the arm port. In any case, its not a ram
issue.
indeed. Please review :)
http://trac.sagemath.org/ticket/15921
On Friday, May
The OSX 10.9 buildbot should have the latest xcode, or at least at most 1-2
months old. Definitely = 5.x.
On Wednesday, May 7, 2014 6:36:43 PM UTC+2, leif wrote:
Should we put up signs telling people not to use the MacOS X pre-built
binaries (or the MacOS X app) with Xcode versions = 5.x?
On Friday, May 9, 2014 5:57:09 PM UTC+2, Peter Bruin wrote:
I just opened a ticket http://trac.sagemath.org/ticket/16311, but I
thought I'd also send a message to sage-devel to advertise the fact that we
can't rely on that doctest to ensure backwards compatibility of our
unpickling
Volker Braun wrote:
The OSX 10.9 buildbot should have the latest xcode, or at least at most
1-2 months old. Definitely = 5.x.
So such issues will vanish with the Sage 6.2+ MacOS X binaries (provided
MacOS X users with recent versions of Xcode use recent [pre-built]
versions of Sage as
Hi Volker,
On Friday, May 9, 2014 5:57:09 PM UTC+2, Peter Bruin wrote:
I just opened a ticket http://trac.sagemath.org/ticket/16311, but I
thought I'd also send a message to sage-devel to advertise the fact that we
can't rely on that doctest to ensure backwards compatibility of our
On 5/9/14 4:40 AM, leif wrote:
Anne Schilling wrote:
We actually added tests for our k-Schur function book. But a lot of
time, when syntax in
Sage changes, these tests just get replaced by others without checking
with the authors
of the book/paper.
git log
Anne Schilling wrote:
On 5/9/14 4:40 AM, leif wrote:
Anne Schilling wrote:
We actually added tests for our k-Schur function book. But a lot of
time, when syntax in
Sage changes, these tests just get replaced by others without checking
with the authors
of the book/paper.
git log
(CCd to sage-devel)
On 5/9/14, 13:32, David Guichard wrote:
Is there some deep reason I'm not seeing that G-S doesn't work for SR?
It seems like everything should be fine. Is the problem in detecting
dependent sets over SR? This keeps me from being able to do simple
examples for a linear
Hi group:
I have been trying to build the doc for SAGE 6.2 on a Mac OSX 10.9.2. The
doc build always stops at:
[tensor ] writing output... [ 75%] sage/tensor/differential_form_element
[tensor ] writing output... [100%] sage/tensor/differential_forms
[tensor ] dumping object inventory...
FTR, that is https://groups.google.com/forum/#!topic/sage-devel/QP34tOWDw-0 and
it's on my Ubuntu 12.04 LTS (quad core Intel) laptop.
On Friday, May 9, 2014 12:37:30 PM UTC-7, KnS wrote:
Hi group:
I have been trying to build the doc for SAGE 6.2 on a Mac OSX 10.9.2. The
doc build always
On 2014-05-09, leif not.rea...@online.de wrote:
Volker Braun wrote:
The OSX 10.9 buildbot should have the latest xcode, or at least at most
1-2 months old. Definitely = 5.x.
So such issues will vanish with the Sage 6.2+ MacOS X binaries (provided
MacOS X users with recent versions of Xcode
Hello,
I've rebased a branch on top of 6.2, which went fine (branch just adds a
file), but then I couldn't push it via git push ... or git trac push with
git insisting that I have to pull. While that worked, it automatically
created an empty (=no files have changed) merge commit listing all my
On 05/09/2014 07:10 PM, Andrey Novoseltsev wrote:
Hello,
I've rebased a branch on top of 6.2, which went fine (branch just adds a
file), but then I couldn't push it via git push ... or git trac push
with git insisting that I have to pull. While that worked, it
automatically created an empty
On Friday, 9 May 2014 17:37:02 UTC-6, Michael Orlitzky wrote:
On 05/09/2014 07:10 PM, Andrey Novoseltsev wrote:
Hello,
I've rebased a branch on top of 6.2, which went fine (branch just adds a
file), but then I couldn't push it via git push ... or git trac push
with git insisting
On Friday, 9 May 2014 17:49:58 UTC-6, Andrey Novoseltsev wrote:
On Friday, 9 May 2014 17:37:02 UTC-6, Michael Orlitzky wrote:
On 05/09/2014 07:10 PM, Andrey Novoseltsev wrote:
Hello,
I've rebased a branch on top of 6.2, which went fine (branch just adds
a
file), but then I
34 matches
Mail list logo
