Origin of eval()-ing in separate namespace object

From	Kalinni Gorzkis <musicdenotation@gmail.com>
Subject	Origin of eval()-ing in separate namespace object
Date	2013-12-08 17:35 +0700
Newsgroups	comp.lang.python
Message-ID	<mailman.3727.1386506211.18130.python-list@python.org> (permalink)

Show all headers | View raw

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?

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Origin of eval()-ing in separate namespace object Kalinni Gorzkis <musicdenotation@gmail.com> - 2013-12-08 17:35 +0700
  Re: Origin of eval()-ing in separate namespace object rusi <rustompmody@gmail.com> - 2013-12-08 05:45 -0800
    Re: Origin of eval()-ing in separate namespace object Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2013-12-08 16:39 +0200
      Re: Origin of eval()-ing in separate namespace object rusi <rustompmody@gmail.com> - 2013-12-08 08:39 -0800

csiph-web