Re: Origin of eval()-ing in separate namespace object

2013-12-08 Thread rusi
On Sunday, December 8, 2013 8:09:39 PM UTC+5:30, Jussi Piitulainen wrote: > rusi writes: > > On Sunday, December 8, 2013 4:05:54 PM UTC+5:30, Kalinni Gorzkis wrote: > > > By which languages(s) Python was inspired to support evaluating > > > expressions and executing statements in a separate "names

Re: Origin of eval()-ing in separate namespace object

2013-12-08 Thread Jussi Piitulainen
rusi writes: > On Sunday, December 8, 2013 4:05:54 PM UTC+5:30, Kalinni Gorzkis wrote: > > > By which languages(s) Python was inspired to support evaluating > > expressions and executing statements in a separate "namespace" > > object? > > > This syntax: > > eval(expression,globals) or exec(code,

Re: Origin of eval()-ing in separate namespace object

2013-12-08 Thread rusi
On Sunday, December 8, 2013 4:05:54 PM UTC+5:30, Kalinni Gorzkis wrote: > By which languages(s) Python was inspired to support evaluating expressions > and executing statements in a separate “namespace” object? > This syntax: > eval(expression,globals) or exec(code,globals) > What is the origin o

Origin of eval()-ing in separate namespace object

2013-12-08 Thread Kalinni Gorzkis
By which languages(s) Python was inspired to support evaluating expressions and executing statements in a separate “namespace” object? This syntax: eval(expression,globals) or exec(code,globals) What is the origin of the functionality provided by the globals argument? -- https://mail.python.org/