Hi all,
I triggered a problem by writing a very simple python file, which only contains
one line :
from sage.matrix.matrix_mod2_dense cimport Matrix_mod2_dense
then, inside sage, running
sage: load "mini_problem.spyx"
raises an error :
sage: load "mini_problem.spyx"
Comp
Yes Nils, In fact it was a browser problem. William makes me notice it.
Thank you all.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
Jason and others,
I attached I prototype of my previous proposal.
What is the best place to talk about it? In the group or I should
create a ticket?
Thanks,
Raniere
On Tue, Sep 25, 2012 at 2:24 PM, Jason Grout
wrote:
> On 9/25/12 12:15 PM, Raniere Gaia Silva wrote:
>>
>> Hi,
>> I would like as
On Oct 8, 9:30 am, Dox wrote:
> Sorry It's not getting updated.
Is it still not updated if you explicitly request a reload in your
browser? As far as I can see, reevaluating a cell does cause
full_output.txt to be rewritten with new content. It could be just
your browser being reluctant to ch
Sorry It's not getting updated.
On Monday, 8 October 2012 12:14:42 UTC-3, Simon King wrote:
>
> Hi!
>
> On 2012-10-08, Dox > wrote:
> > --=_Part_110_6376496.1349698687928
> > Content-Type: text/plain; charset=ISO-8859-1
> > ...
> > I noticed that after changing the variables, and reru
Hi!
On 2012-10-08, Dox wrote:
> --=_Part_110_6376496.1349698687928
> Content-Type: text/plain; charset=ISO-8859-1
> ...
> I noticed that after changing the variables, and rerun the calculation the
> full_output.txt is now getting updated.
>
> I guess this is a bug.
Why?
If one reruns a cal
I have experienced this on sagenb.org.
Regards,
Ifti
On Oct 8, 2012, at 5:48 PM, Dox wrote:
> Dear community:
>
> I was doing some simple linear algebra calculations, and since the output was
> a long list, Sage gave me a few lines with the option of looking at the
> full_output.txt file.
>
On 2012-10-08 15:00, Jeroen Demeyer wrote:
> While testing sage-5.4, I discovered the following rare doctest error:
>
> sage -t --long -force_lib devel/sage/sage/modular/modform/ambient.py
> you are running out of primes. 1000 coprime primes
> found
Just to state the obvious: "you are running out of primes. 1000 coprime
primes found" doesn't sound good. Maybe thats where you are sporadically
unlucky?
On Monday, October 8, 2012 2:00:10 PM UTC+1, Jeroen Demeyer wrote:
>
> While testing sage-5.4, I discovered the following rare doctest error
While testing sage-5.4, I discovered the following rare doctest error:
sage -t --long -force_lib devel/sage/sage/modular/modform/ambient.py
you are running out of primes. 1000 coprime primes
found**
File
"/release/buildbot/sage/s
>From the installation guide:
>
>> SAGE_TESTDIR - a temporary directory used during Sage’s doctesting.
>> The default is to use the directory $DOT_SAGE/tmp, but you can override
>> that by setting this variable.
>>
>> So try setting this environment variable. You could also set DOT_SAGE to
On Friday, October 5, 2012 1:32:34 PM UTC-4, John H Palmieri wrote:
>
>
>
> On Friday, October 5, 2012 10:09:38 AM UTC-7, kcrisman wrote:
>>
>>
>>
>>> User 1@GCO2635 /home/newsagetest/sage-5.4.rc0/devel/sage
>>> $../../sage -t sage/functions/piecewise.py
>>> sage -t "devel/sage-main/sage/function
Dear community:
I was doing some simple linear algebra calculations, and since the output
was a long list, Sage gave me a few lines with the option of looking at the
full_output.txt file.
I noticed that after changing the variables, and rerun the calculation the
full_output.txt is now getting
On 2012-10-08 00:30, Charles Bouillaguet wrote:
> Traceback (most recent call last):
> File "/Users/cbouilla/Desktop/sage-5.3/local/bin/sage-sagex", line 5, in
>
> from sage.misc.interpreter import load_sagex
> ImportError: cannot import name load_sagex
>
> Is this normal ? Am I doing some
14 matches
Mail list logo
