On 23 May 2009, at 07:31, Pat LeSmithe wrote:
> > > In some circumstances, "Stein's trick" may help [1]: > > class myint: > def eval(self, s, globals, locals): > _temp = locals['Integer'] > locals['Integer'] = float > ans = python.eval(preparse(s), globals, locals) > locals['Integer'] = _temp > return ans > > Examples, in separate cells: > > %myint() > print type(45) > print 500 / 1000, 1000 / 1000 > print 500 / 1000., 1000 / 1000. > > <type 'float'> > 0.5 1.0 > 0.500000000000000 1.00000000000000 > > print type(45) > print 500 / 1000, 1000 / 1000 > print 500 / 1000., 1000 / 1000. > > <type 'sage.rings.integer.Integer'> > 1/2 1 > 0.500000000000000 1.00000000000000 > > Modular arithmetic, Python 'int', and matplotlib.pyplot examples at > [2]. > I don't why the extra point at the origin shows up. > > [1] https://groups.google.com/group/sage-devel/msg/e53caae140cef7df > [2] http://www.sagenb.org/home/pub/563/ > Thanks for the info on a possible workaround. This may be a workable solution to my problem, at least until sage and matplotlib learn to play more nicely together. If that day ever arrives, it wouldn't be much work to pull all the %myint() lines out of my worksheets. There are side effects though. List slicing doesn't like it. Numpy array slicing is still OK though. -- Kevin Horton Ottawa, Canada --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
