Commit 097bbea4 authored by Georg Brandl's avatar Georg Brandl

evalfile() should be execfile().

 (backport from rev. 51677)
parent 2998a1c2
...@@ -4381,7 +4381,7 @@ the debugger, and that's one reason why this loophole is not closed. ...@@ -4381,7 +4381,7 @@ the debugger, and that's one reason why this loophole is not closed.
makes use of private variables of the base class possible.) makes use of private variables of the base class possible.)
Notice that code passed to \code{exec}, \code{eval()} or Notice that code passed to \code{exec}, \code{eval()} or
\code{evalfile()} does not consider the classname of the invoking \code{execfile()} does not consider the classname of the invoking
class to be the current class; this is similar to the effect of the class to be the current class; this is similar to the effect of the
\code{global} statement, the effect of which is likewise restricted to \code{global} statement, the effect of which is likewise restricted to
code that is byte-compiled together. The same restriction applies to code that is byte-compiled together. The same restriction applies to
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment