Actually, it's extremely rewarding to get the solution presented on a
plate hours after sending a message to support. But you're right, it is
a bit frustrating to have to convert every number to the right python type.
Thanks again for your help!
Stan
Jason Grout wrote:
> Stan Schymanski wrote
Stan Schymanski wrote:
> Of course, pylab.axis([float(0.1),float(3.5),float(0.1),float(3.5)])
> works. Thanks a lot!
>
> Is it a longer term goal to make such type conversions automatic?
YES!
It is pretty frustrating as it is now. I think you'd agree.
Jason
>
> Cheers,
> Stan
>
> Jaso
Of course, pylab.axis([float(0.1),float(3.5),float(0.1),float(3.5)])
works. Thanks a lot!
Is it a longer term goal to make such type conversions automatic?
Cheers,
Stan
Jason Grout wrote:
> Stan Schymanski wrote:
>
>> Hi Jason,
>>
>> your suggestion works, but it is not only related to inte
Oh, OK, this is fixed in 3.4.alpha0, I'm still running 3.3 (which, in
this computer, I compiled from source last week).
On Tue, Mar 17, 2009 at 6:05 PM, Robert Bradshaw
wrote:
>
> On Mar 17, 2009, at 3:02 PM, Luiz Felipe Martins wrote:
>
> [...]
>
>> So, it is not the interface with scipy/pylab
Stan Schymanski wrote:
> Hi Jason,
>
> your suggestion works, but it is not only related to integers, as I get
> the same error message if I use e.g. 0.1, 3.1, 0.1, 3,1 as axis ranges.
> How could I convert sage reals to python reals?
use float(0.1)
Thanks,
Jason
--~--~-~--~~
Hi Jason,
your suggestion works, but it is not only related to integers, as I get
the same error message if I use e.g. 0.1, 3.1, 0.1, 3,1 as axis ranges.
How could I convert sage reals to python reals?
Cheers,
Stan
Jason Grout wrote:
> Stan Schymanski wrote:
>
>> Dear all,
>>
>> Since vers
On Mar 17, 2009, at 3:02 PM, Luiz Felipe Martins wrote:
[...]
> So, it is not the interface with scipy/pylab that changed, but the way
> literals such as 5r are interpreted by Sage.
This was a known bug, and has been fixed. http://trac.sagemath.org/
sage_trac/ticket/5356
>
> On Tue, Mar 17, 2
Here is something I noticed this weekend, running a worksheet I had
originally written in Sage 3.1 or 3.2 (I can't remember).
This gives an error:
sage: from scipy import stats
sage: stats.binom.pmf(5r,10r,0.5r)
Traceback (most recent call last):
...
TypeError: unsupported operand type(s) for *:
Stan Schymanski wrote:
> Dear all,
>
> Since version 3.3, the option "pylab.axis([xmin,xmax,ymin,ymax])"
> leads to an error. Does anyone know what is going wrong there and how
> to get around it?
>
> Example generated in a Sage 3.4 notebook:
>
> import pylab
> pylab.clf()
> pylab.figure(1)
> p
Sorry, here is the full traceback. Thanks for looking into that!
Stan
Traceback (most recent call last):
File "", line 1, in
File
"/Users/sschym/.sage/sage_notebook/worksheets/admin/4/code/33.py", line
11, in
pylab.axis([_sage_const_0 ,_sage_const_3 ,_sage_const_0
,_sage_const_3 ])
Stan Schymanski wrote:
> Dear all,
>
> Since version 3.3, the option "pylab.axis([xmin,xmax,ymin,ymax])"
> leads to an error. Does anyone know what is going wrong there and how
> to get around it?
>
> Example generated in a Sage 3.4 notebook:
>
> import pylab
> pylab.clf()
> pylab.figure(1)
> p
11 matches
Mail list logo
