Extend support for from __future__ import nested_scopes

If a module has a future statement enabling nested scopes, they are
also enable for the exec statement and the functions compile() and
execfile() if they occur in the module.

If Python is run with the -i option, which enters interactive mode
after executing a script, and the script it runs enables nested
scopes, they are also enabled in interactive mode.

XXX The use of -i with -c "from __future__ import nested_scopes" is
not supported.  What's the point?

To support these changes, many function variants have been added to
pythonrun.c.  All the variants names end with Flags and they take an
extra PyCompilerFlags * argument.  It is possible that this complexity
will be eliminated in a future version of the interpreter in which
nested scopes are not optional.

1 files changed, 14 insertions, 2 deletions

diff --git a/Python/bltinmodule.c b/Python/bltinmodule.c
index ec680d1..9a09c8c 100644
--- a/Python/bltinmodule.c
+++ b/Python/bltinmodule.c
@@ -373,7 +373,12 @@ builtin_compile(PyObject *self, PyObject *args)
 		   "compile() arg 3 must be 'exec' or 'eval' or 'single'");
 		return NULL;
 	}
-	return Py_CompileString(str, filename, start);
+	if (PyEval_GetNestedScopes()) {
+		PyCompilerFlags cf;
+		cf.cf_nested_scopes = 1;
+		return Py_CompileStringFlags(str, filename, start, &cf);
+	} else
+		return Py_CompileString(str, filename, start);
 }
 
 static char compile_doc[] =
@@ -808,7 +813,14 @@ builtin_execfile(PyObject *self, PyObject *args)
 		PyErr_SetFromErrno(PyExc_IOError);
 		return NULL;
 	}
-	res = PyRun_FileEx(fp, filename, Py_file_input, globals, locals, 1);
+	if (PyEval_GetNestedScopes()) {
+		PyCompilerFlags cf;
+		cf.cf_nested_scopes = 1;
+		res = PyRun_FileExFlags(fp, filename, Py_file_input, globals, 
+				   locals, 1, &cf);
+	} else 
+		res = PyRun_FileEx(fp, filename, Py_file_input, globals, 
+				   locals, 1);
 	return res;
 }