Thank you, Mr. Drake. I looked at the ticket and understand some of
it. I hope it can be fixed. For now I'll have to put my scripts in
non-white-space and non-ascii paths. -- Lou P
On Feb 18, 9:32 pm, Dan Drake wrote:
> On Fri, 19 Feb 2010 at 11:17AM +0900, Dan Drake wrote:
> > I worked on t
I am sending this to sage-support
On Thursday, February 18, 2010, Joerg Arndt wrote:
> The following doesn't finish in reasonable time:
>
> var('E1, E2, E4, E5, E10, E20');
> var( 'q' );
> t=(E20^16*E5^8*q^4*E2^24 + (-E20^16*E5^8*q^4*E4^8*E1^16 + (-E10^24 +
> E20^8*E
That was was a lot of good feedback! I'll try that
thank you all!
Oscar
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/
Hi,
I downloaded sage-virtualbox-4.3.zip, and installation went well.
However, the second time I tried to use Virtualbox, I got the message
"Configuring network ...". And now Firefox 3.5.8 can not find http:\
\192.168.56.101
What to do? Thanks in advance for a swift response! Roland
--
To post t
Python json library is of simple use but there's this problem:
sage: import json
sage: json.dumps( {"a": 1.8} )
...produce an error because:
sage: x = 1.8
sage: type(x)
Should one do the "type cast" below for every int or float when using
sage ?
sage: type(float(x))
sage: json.dumps( {"a": flo
On Fri, Feb 19, 2010 at 3:52 PM, jpc wrote:
> Should one do the "type cast" below for every int or float when using
> sage ?
>
> sage: type(float(x))
>
> sage: json.dumps( {"a": float(x)} )
> '{"a": 1.8}'
>
> Any easier way ?
You write a custom encoder to do this:
http://docs.python.org/librar
