On Jan 26, 2010, at 2:04 AM, Dag Sverre Seljebotn wrote:
I think a case can be made for *always* enabling the __future__ imports that Cython provides, i.e. just add it to the pyx_preparse prefix string. After all, really long-term (Python 3-land) they will be the defaults anyway, and with Sage code true division already is the default behaviour.
True division is not the default behavior--we create rational numbers (which Python doesn't have) rather than numerical approximations.
Or will that break too many worksheets?
It's not something I'd like to spring on people, especially as unicode_literals doesn't play well with char* conversions. The only others we support are with_statement (never turned off, as there's no "old" behavior) and division.
Given that __future__ must be the first statement in a file, except for a docstring, it shouldn't be too hard to parse out. (Well, parsing out the docstring can be a pain...)
- Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
