Re: [sage-devel] Is it really a feature that sage_eval() doesn't access globals?

2015-03-30 Thread William Stein
On Mon, Mar 30, 2015 at 5:58 AM, Jeroen Demeyer wrote: > The documentation of sage_eval() seems to indicate that this is a feature: > > sage: a=5 > sage: sage_eval("a+1") > ... > NameError: name 'a' is not defined > > Of course you can do > > sage: a = 5 > sage: sage_eval("a+1", locals={'a':a}) >

[sage-devel] Is it really a feature that sage_eval() doesn't access globals?

2015-03-30 Thread Jeroen Demeyer
The documentation of sage_eval() seems to indicate that this is a feature: sage: a=5 sage: sage_eval("a+1") ... NameError: name 'a' is not defined Of course you can do sage: a = 5 sage: sage_eval("a+1", locals={'a':a}) 6 But I'm wondering if sage_eval() with globals shouldn't "just work". The