Le 23/12/2012 18:13, Julien Puydt a écrit :
I was all for throwing atlas a few days ago ; I have since been in touch
with Clint Whaley (reporting upstream my issues with #10508 [1]), and he
has been extremely reactive and efficient. That has definitely softened
my point of view on the matter.
Man, still no success in getting through the libm4rie build. It ran for 38
hours before I had to get ready to head back to North America (which
involved cutting power to the Pi). It looks like the swap (on a connected
usb drive) just got so jammed up after a couple hours that the work was
Le 24/12/2012 11:28, tom d a écrit :
Man, still no success in getting through the libm4rie build.
I think we should report it as a bug upstream.
Snark on #sagemath
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To post to this group, send
On Monday 24 Dec 2012, tom d wrote:
Man, still no success in getting through the libm4rie build. It ran for 38
hours before I had to get ready to head back to North America (which
involved cutting power to the Pi). It looks like the swap (on a connected
usb drive) just got so jammed up after
Le 24/12/2012 12:53, Martin Albrecht a écrit :
On Monday 24 Dec 2012, tom d wrote:
Man, still no success in getting through the libm4rie build. It ran for 38
hours before I had to get ready to head back to North America (which
involved cutting power to the Pi). It looks like the swap (on a
Does anybody have an explanation why this segfaults while importing
Twisted? You are doctesting sage/modules/module.pyx, that shouldn't have
anything to do with web servers or internet access.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To
On Monday, December 24, 2012 2:23:24 PM UTC+1, Volker Braun wrote:
Does anybody have an explanation why this segfaults while importing
Twisted? You are doctesting sage/modules/module.pyx, that shouldn't have
anything to do with web servers or internet access.
I think that is because the
Helloo everybody !!
I finally found out where my bug from [1] was coming from !
It seems to come from the fact that I installed Sage in the directory
$HOME/.Sage/. And Sage does not like that. Actually, it refuses to test any
file whose path contains /. and so of course thinks that there is
And I'm on a truly measly 256mb of RAM, but with 2gb swap.
Thanks for taking some time to consider this!
On Monday, December 24, 2012 2:53:56 PM UTC+3, Martin Albrecht wrote:
On Monday 24 Dec 2012, tom d wrote:
Man, still no success in getting through the libm4rie build. It ran for
38
Hi,
By the way, I realized that membership in RDF and CDF is completely broken:
sage: vector( [1, 2, sqrt(-1)] ) in RDF^3
True # o_O
sage: R.x = QQ[]
sage: vector( [1,x] ) in CDF^2
True # O_o
and of course :
sage: vector( RDF, [1, 2, sqrt(-1)] )
Sometimes the best strategy for fixing a bug is to not look for it, but
to rewrite the program from scratch.
I don't know what exactly you are trying to do, but surely you are not
using ALL of Sage.
If your concern is to complete some computation, can you do so without
trying to debug Sage --
On Dec 24, 2012, at 3:59 PM, Charles Bouillaguet wrote:
Hi,
By the way, I realized that membership in RDF and CDF is completely broken:
sage: vector( [1, 2, sqrt(-1)] ) in RDF^3
True # o_O
sage: R.x = QQ[]
sage: vector( [1,x] ) in CDF^2
True # O_o
This happens because
On Monday, December 24, 2012 3:04:55 PM UTC+1, Jean-Pierre Flori wrote:
On Monday, December 24, 2012 2:23:24 PM UTC+1, Volker Braun wrote:
Does anybody have an explanation why this segfaults while importing
Twisted? You are doctesting sage/modules/module.pyx, that shouldn't have
Not sure we got these so clearly before, but using --without-pymalloc and
Valgrind (hint: finish and review #13060) I get lots of
==28631== Invalid read of size 8
==28631==at 0x10429E50:
__pyx_tp_dealloc_4sage_9structure_15category_object_CategoryObject
(category_object.c:8990)
==28631==
Hi Jean-Pierre,
On 2012-12-24, Jean-Pierre Flori jpfl...@gmail.com wrote:
Not sure we got these so clearly before, but using --without-pymalloc and
Valgrind (hint: finish and review #13060) I get lots of
==28631== Invalid read of size 8
==28631==at 0x10429E50:
On Monday, December 24, 2012 10:54:48 PM UTC+1, Simon King wrote:
Hi Jean-Pierre,
On 2012-12-24, Jean-Pierre Flori jpf...@gmail.com javascript: wrote:
Not sure we got these so clearly before, but using --without-pymalloc
and
Valgrind (hint: finish and review #13060) I get lots of
On Monday, December 24, 2012 11:18:26 PM UTC+1, Jean-Pierre Flori wrote:
On Monday, December 24, 2012 10:54:48 PM UTC+1, Simon King wrote:
Hi Jean-Pierre,
On 2012-12-24, Jean-Pierre Flori jpf...@gmail.com wrote:
Not sure we got these so clearly before, but using --without-pymalloc
On Tuesday, December 25, 2012 1:44:01 AM UTC+1, Jean-Pierre Flori wrote:
On Monday, December 24, 2012 11:18:26 PM UTC+1, Jean-Pierre Flori wrote:
On Monday, December 24, 2012 10:54:48 PM UTC+1, Simon King wrote:
Hi Jean-Pierre,
On 2012-12-24, Jean-Pierre Flori jpf...@gmail.com
On 12/23/12 11:37 AM, Volker Braun wrote:
On a related note, does anybody know MAGMA (not the number theory
system, silly). The BLAS implementation, aka Matrix Algebra on GPU and
Multicore Architectures: http://icl.cs.utk.edu/magma/
I've been keeping an eye on MAGMA and PLASMA.
Also, the
19 matches
Mail list logo
