On Mon, Aug 22, 2011 at 10:23 AM, Chris Seberino <cseber...@gmail.com> wrote: > > On Aug 22, 10:28 am, v...@ukr.net wrote: >> It seems to me that interpreting the "f (x)" as "f*x" could easily >> confuse the people who are new to Python and Sage. They will read (or >> maybe have already read) some book on Python and the will try to apply >> their new knowledge in Sage, but instead will find some strange >> inexplicable (at first glance) behaviour. >> Wouldn't it be better to stick to Zen of Python rule #2 in this case? >> >> "Explicit is better than implicit." > > As kcrisman said, this would only be an option. > Also, I think "f(x)" is more explicit than "f (x)". > > I never use "f (x)" in Python code and wonder why it is even allowed > in Python instead of raising an exception.
Wow, that's almost as bad as "I didn't put any cheese on the eggs for the vegan." which I just overheard hear at Sage Days 32 from the chef. -- William > > cs > > -- > 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 > URL: http://www.sagemath.org > -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 URL: http://www.sagemath.org