On Mon, Mar 19, 2018 at 2:06 PM, Nicolas M. Thiery <nicolas.thi...@u-psud.fr> wrote: > On Thu, Mar 15, 2018 at 08:49:02AM -0700, William Stein wrote: >> On Thu, Mar 15, 2018 at 7:43 AM, Emmanuel Charpentier >> <emanuel.charpent...@gmail.com> wrote: >> > [...] However, most CASes now available do away without this mandatory >> > declaration. >> >> And hence Sage should have automatic_names as a non-default *option*. > > Yeah; it's all a balance between simplicity vs risk of confusion. From > using, teaching, and witnessing people teach SageMath, there are some > contexts where you (or more likely your teacher!) know what you are > doing, there is no risk of confusion, and simplicity primes. Most of > the time we don't want it though. So +1 as well on automatic_names as > an option not set by default. Also +1 on the message when a variable > is created. > > Finally, I could suggest to write it as: > > %automatic_names
+1 I like the idea of making it a magic. I would still probably keep the automatic_names() function for backwards-compatibility. But maybe, at least when running in IPython, display a deprecation warning in favor of %automatic_names. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
