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: > >> 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 >> >> Jason Grout wrote: >> >>> 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 >>> >>> >>> >>> >>> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
