>
> It is not obvious (for non-experts) that this is the elegant and preferred
> route. It would be nice if this 'solution' was mentioned somewhere.
>
>
This could be something to put in the Sage developer manual under
conventions.
> As part of the function, or when an ValueError is raised,
>> Another possibility is to use a snapshot image for each desktop or
>> something - that is what some admins I know do, though I confess I do not
>> know how that works. Maybe your situation is not a lab.
>>
>
> I'm not sure I understand what you are suggesting here. I do have a lab,
> so i
On Dec 5, 2014, at 9:36 AM, Jérôme Tremblay
wrote:
On Friday, December 5, 2014 11:32:34 AM UTC-5, kcrisman wrote:
> When I run sage as admin, everything works fine. However, when my users
>> try to run Sage, they get a warning that they are trying to execute Sage
>> from a read-only filesystem.
Dear William,
Thanks for your reply and thoughtful example.
It is not obvious (for non-experts) that this is the elegant and preferred
route. It would be nice if this 'solution' was mentioned somewhere.
As part of the function, or when an ValueError is raised, or on a Quick
Reference Card, o
On Friday, December 5, 2014 11:32:34 AM UTC-5, kcrisman wrote:
>
> When I run sage as admin, everything works fine. However, when my users
>> try to run Sage, they get a warning that they are trying to execute Sage
>> from a read-only filesystem.
>>
>>
> This was implemented in http://trac.sage
>
> When I run sage as admin, everything works fine. However, when my users
> try to run Sage, they get a warning that they are trying to execute Sage
> from a read-only filesystem.
>
>
This was implemented in http://trac.sagemath.org/ticket/15732 because Sage
needs to write to some files in .s
Under OSX Yosemite, I try to install Sage 6.4.1 app in the system
applications.
When I run sage as admin, everything works fine. However, when my users try
to run Sage, they get a warning that they are trying to execute Sage from a
read-only filesystem.
My question is :
It it safe to execute
On Fri, Dec 5, 2014 at 7:38 AM, kcrisman wrote:
> Hmm, this is a fairly old function, if I recall correctly, implemented
> relatively early on.There may be some discussion from where it was
> upgraded at http://trac.sagemath.org/ticket/16308 or
> http://trac.sagemath.org/ticket/16374 (I cannot
Hmm, this is a fairly old function, if I recall correctly, implemented
relatively early on.There may be some discussion from where it was
upgraded at http://trac.sagemath.org/ticket/16308
or http://trac.sagemath.org/ticket/16374 (I cannot find the original
ticket, which surprises me).
So i
> Is it possible to choose different fontsize(s) for the axis labels and the
> numbers in the axis?
>
> I'm particularly interested in the `implicit_plot` function, but if it
> works in a usual `plot` is good enough!!!
>
> Thank you.
>
Good question!
See
http://sagemath.org/doc/reference/pl
Is it possible to choose different fontsize(s) for the axis labels and the
numbers in the axis?
I'm particularly interested in the `implicit_plot` function, but if it
works in a usual `plot` is good enough!!!
Thank you.
--
You received this message because you are subscribed to the Google Gr
Hi, please look at the following example.
sage: print two_squares(3437458237428)
Traceback (most recent call last):
...
ValueError: 3437458237428 is not a sum of 2 squares
The ouput is an error message. Thus if I want to test several cases, I have
to check each case like:
sage: for k in xrange
On Thu, 4 Dec 2014, Nils Bruin wrote:
It's more surprising to me that Scipy can eat a Sage matrix, actually.
Fredrik, any thoughts?
Indeed mpmath can do this too but is a little picky about lists/tuples
vs. iterables:
sage: mp.matrix(tuple(tuple(m) for m in M))
You wouldn't want to do
13 matches
Mail list logo
