Recently in a different thread here [1], someone accidentally clobbered a Python builtin with a symbolic function:
sage: t = (1,2,3) sage: len(t) = 4 ...which overwrites t and the Python builtin len. I have a patch at #14231 that, at Nils Bruin's suggestion, *always* prints when defining a symbolic function via the preparser: sage: f(u,v)=u+v Defining symbolic function f and symbolic variables u,v This makes it easier to catch typos such as "sin(t) = 0" when you want "sin(t) == 0". This seems reasonable to me; I taught the MAA PREP workshop on Sage last summer, and symbolic functions and variables were a tricky concept. The new behavior would at least tell the user what the preparser is doing behind the scenes. This is a change in behavior, though, and will require fixing a lot of doctests. Comments welcome. Dan References: [1] https://groups.google.com/forum/?fromgroups=#!topic/sage-devel/EQzNB7vkN3o -- --- Dan Drake ----- http://math.pugetsound.edu/~ddrake -------
signature.asc
Description: Digital signature
