Hi, Dozens of times over the years, people have complained because in Sage symbolic variables names don't magically spring into existence, and also about object-oriented method call notation. We have defended this design forever, not even considering providing a non-default optional mode what variables do spring into existence etc. Well not anymore.
sage: automatic_names(True) sage: x + y + z + wxy wxy + x + y + z sage: y(y=10) 10 sage: type(y) <class 'sagenb.misc.support.AutomaticVariable'> sage: trig_expand((2*x + 4*y + sin(2*theta))^2) 4*(sin(theta)*cos(theta) + x + 2*y)^2 Try this now at http://alpha.sagenb.org Also see the ticket with a patch that needs review: http://trac.sagemath.org/sage_trac/ticket/7482 First there is a little simple demo code so one can play with this. Then there is a real much more carefully thought through patch. Can somebody referee this? It's mainly code in the *notebook* -- it doesn't seem possible to do something like the above on the command line without some deep internal change to Ipython. Let me know if you're interesting in refereeing this but find the combination of messing with the sagenb code and sage library too daunting. -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- 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
