On Sun, Apr 13, 2008 at 1:20 PM, David Roe <[EMAIL PROTECTED]> wrote: > > On the other hand, using a leading zero to indicate octal is a fairly > standard convention in computer science. And it's nice to minimize > these kinds of differences between Python ints and Sage Integers. > David >
+1. Also in choosing between consistency with Python and consistency with a high school teacher, we should (usually) go with consistency with Python. Also, I bet there are also many high school teachers out there who would say that a 0 in the front of integer means octal (since this is a convention in computer science). They might not say that in their math class, but would in their CS class... > On Sun, Apr 13, 2008 at 3:36 PM, Harald Schilly > > <[EMAIL PROTECTED]> wrote: > > > > > > On Apr 13, 9:08 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > > the other option -- changing > > > Python -- is not an option. > > > > > > > I know, but my "picture" is a high-school teacher explaining that > > leading zeros don't matter, and when someone tries it in sage, it > > suddenly matters. So, imho, there is something not ok with that. The > > preparser could filter this, also depending its behaviour based on the > > current mode. And the inconsistency should be fixed, too. > > > > Harald > > > > > > > > > > > > > -- 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
