On Mon, May 25, 2009 at 6:54 AM, Wilfried_Huss
<h...@finanz.math.tugraz.at> wrote:
>
> With the new symbolics I get the following error:
>
> sage: a(x) = x
> sage: print a(x)
> ERROR: An unexpected error occurred while tokenizing input
> The following traceback may be corrupted or invalid
> The error message is: ('EOF in multi-line statement', (2440, 0))
> (...)
> AttributeError: 'module' object has no attribute 'float128'This is a known bug on 32-bit computers. I think we import numpy's (?) float128 somewhere, and since we did all development on 64-bit, we didn't notice this problem until after releasing rc0. On 64-bit it works fine: wst...@sage:~$ build/sage-4.0.rc0/sage ---------------------------------------------------------------------- | Sage Version 4.0.rc0, Release Date: 2009-05-21 | | Type notebook() for the GUI, and license() for information. | ---------------------------------------------------------------------- sage: a(x) = x sage: print a(x) x sage: is_64_bit True I think unfortunately some of us have lost some momentum on 4.0 due to post Sage-days exhaustion. William > > Calling the same statement a second time now works: > > sage: print a(x) > x > > cheers, > Wilfried Huss > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
