On 4/21/11 11:16 PM, ancienthart wrote:
Kelvin's suggestion is the easiest. This is how I run sage on my windows
work machine, inside virtualbox on ubuntu. The vmware image provided on
the website lacks R png support, so I like to roll my own.
We just investigated this issue, and it appears th
Kelvin's suggestion is the easiest. This is how I run sage on my windows
work machine, inside virtualbox on ubuntu. The vmware image provided on the
website lacks R png support, so I like to roll my own.
Joal Heagney
--
To post to this group, send email to sage-support@googlegroups.com
To unsu
> > My oracle VM stopped working a while ago, the wmware stopped today
> > with some bug
> > widely discussed on the web due to windows 7 updates, and the wubi
> > failed to install at all.
> >
> > What should be the safest way against these type of problems?
In my personal experience, I have bee
Hi!
On 21 Apr., 18:23, tvn wrote:
> Hi, sorry I still don't get this.
>
> If I write my code in a test.sage file -- then load or attach it from Sage
> interactive. Then how do I call doctest on it ? Previously I write my
> code in a test.py file , then from Sage interactive session I call im
On Thursday, April 21, 2011 6:33:43 PM UTC+2, kuhn wrote:
>
> What should be the safest way against these type of problems?
>
Install a linux distribution designed for long-term stability like
RHEL/Scientific Linux or Debian.
--
To post to this group, send email to sage-support@googlegroups.co
My oracle VM stopped working a while ago, the wmware stopped today
with some bug
widely discussed on the web due to windows 7 updates, and the wubi
failed to install at all.
What should be the safest way against these type of problems?
--
To post to this group, send email to sage-support@goo
Hi, sorry I still don't get this.
If I write my code in a test.sage file -- then load or attach it from Sage
interactive. Then how do I call doctest on it ? Previously I write my
code in a test.py file , then from Sage interactive session I call import
test , then doctest.testmod(test)
Indeed a line beginning with ">>> " is not preparsed, whereas a line
beginning with "sage: " is. Continuation lines seem to have weird behavior
(fixing this is trac #10458 which sort of petered out).
Here are some examples: http://pastebin.com/qE98z21b
-Keshav
Join us in #sagemath on irc.
On Apr 21, 2011, at 01:47 , Simon King wrote:
> Hi!
>
> On 21 Apr., 06:45, "Justin C. Walker" wrote:
>>> def test(p):
>>>"""
>> var('x')
>>>x
>> test(1/2*x)
>>>1/2*x
>>>"""
>>>print p
>> ...
>>
>> You are using a ".py" file, so Sage treats it as python (not Sage) co
Hi!
On 21 Apr., 06:45, "Justin C. Walker" wrote:
> > def test(p):
> > """
> var('x')
> > x
> test(1/2*x)
> > 1/2*x
> > """
> > print p
> ...
>
> You are using a ".py" file, so Sage treats it as python (not Sage) code. It
> doesn't get preparsed using Sage's rules. In p
10 matches
Mail list logo
