[Python-checkins] r82836 - in python/branches/release31-maint: Doc/tutorial/classes.rst

[mark.dickinson]

Author: mark.dickinson
Date: Mon Jul 12 11:39:08 2010
New Revision: 82836

Log:
Merged revisions 82835 via svnmerge from 
svn+ssh://pythondev@svn.python.org/python/branches/py3k

........
  r82835 | mark.dickinson | 2010-07-12 10:37:40 +0100 (Mon, 12 Jul 2010) | 1 line
  
  Remove mention of execfile from the tutorial.
........


Modified:
   python/branches/release31-maint/   (props changed)
   python/branches/release31-maint/Doc/tutorial/classes.rst

Modified: python/branches/release31-maint/Doc/tutorial/classes.rst
==============================================================================
--- python/branches/release31-maint/Doc/tutorial/classes.rst	(original)
+++ python/branches/release31-maint/Doc/tutorial/classes.rst	Mon Jul 12 11:39:08 2010
@@ -599,12 +599,12 @@
 possible to access or modify a variable that is considered private.  This can
 even be useful in special circumstances, such as in the debugger.
 
-Notice that code passed to ``exec()``, ``eval()`` or ``execfile()`` does not
-consider the classname of the invoking  class to be the current class; this is
-similar to the effect of the  ``global`` statement, the effect of which is
-likewise restricted to  code that is byte-compiled together.  The same
-restriction applies to ``getattr()``, ``setattr()`` and ``delattr()``, as well
-as when referencing ``__dict__`` directly.
+Notice that code passed to ``exec()`` or ``eval()`` does not consider the
+classname of the invoking class to be the current class; this is similar to the
+effect of the ``global`` statement, the effect of which is likewise restricted
+to code that is byte-compiled together.  The same restriction applies to
+``getattr()``, ``setattr()`` and ``delattr()``, as well as when referencing
+``__dict__`` directly.
 
 
 .. _tut-odds: