#17958: implement declare_var, deprecate (None)var
-----------------------------+------------------------
Reporter: rws | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.6
Component: symbolics | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-----------------------------+------------------------
Comment (by kcrisman):
> > seems cleaner. Maybe it's not all due to confusion.
> I'm not quite clear whether you mean:
> - side-effectful routines should NOT return a value (quite standard)
and should NOT print something.
> - side-effectful routines are unclean anyway and it's no bother to type
`a=var('a')`.
What I mean is that I think the doctests were written that way because it
was easier to type`a=var('a')` than have to deal with an output. For
myself, I think that
* keeping previous behavior
* ease of use
argue strongly for `var('a')` or something else ''easy'', no equals signs
etc. In fact, `var(a)` would be easiest but Python wouldn't allow that.
--
Ticket URL: <http://trac.sagemath.org/ticket/17958#comment:34>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
