On Tue, Jun 16, 2009 at 3:55 PM, Utpal Sarkar<doe...@gmail.com> wrote:
>
> I think global=False would be a nice option, also because there seem
> to be more differences between a symbolic variable created using "var"
> and "new_var" than just the scope; I noticed that while "var" creates
> a symbolic variable, "new_var" creates an expression (class
> 'sage.symbolic.expression.Expression') which cannot be used in the
> same way, e.g. solve_mod(3*x == 1, 10) is ok for x created using "var"
> but causes an error for x created using "new_var".
You can also do
sage: SR.var('x')
x
which returns the variable but does not inject anything into the
global namespace.
--Mike
--~--~---------~--~----~------------~-------~--~----~
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
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
