From: Georg Brandl <georg@python.org>
Date: Fri, 1 Sep 2006 22:30:52 +0000 (+0000)
Subject: evalfile() should be execfile().
X-Git-Tag: v2.6a1~2727
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f29882d8e747deb3967c62a14d4285260b2cad89;p=python

evalfile() should be execfile().
---

diff --git a/Doc/tut/tut.tex b/Doc/tut/tut.tex
index fb5c4f299d..554d094fa8 100644
--- a/Doc/tut/tut.tex
+++ b/Doc/tut/tut.tex
@@ -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.)
 
 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 
 \code{global} statement, the effect of which is likewise restricted to 
 code that is byte-compiled together.  The same restriction applies to