summaryrefslogtreecommitdiffstats
path: root/Python/future.c
diff options
context:
space:
mode:
authorTim Peters <tim.peters@gmail.com>2001-07-16 02:29:45 (GMT)
committerTim Peters <tim.peters@gmail.com>2001-07-16 02:29:45 (GMT)
commit5ba58662817b708a453020f0425fe4747ea6d5cb (patch)
tree7d53f1d02fdcc9f6ce4bd1e5130ba1f57269bb3f /Python/future.c
parent4dbf87152eb69e8c8c87d3081630c4bc02d7cace (diff)
downloadcpython-5ba58662817b708a453020f0425fe4747ea6d5cb.zip
cpython-5ba58662817b708a453020f0425fe4747ea6d5cb.tar.gz
cpython-5ba58662817b708a453020f0425fe4747ea6d5cb.tar.bz2
Part way to allowing "from __future__ import generators" to communicate
that info to code dynamically compiled *by* code compiled with generators enabled. Doesn't yet work because there's still no way to tell the parser that "yield" is OK (unlike nested_scopes, the parser has its fingers in this too). Replaced PyEval_GetNestedScopes by a more-general PyEval_MergeCompilerFlags. Perhaps I should not have? I doubted it was *intended* to be part of the public API, so just did.
Diffstat (limited to 'Python/future.c')
-rw-r--r--Python/future.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/Python/future.c b/Python/future.c
index 70be26b..f0960ae 100644
--- a/Python/future.c
+++ b/Python/future.c
@@ -32,7 +32,7 @@ future_check_features(PyFutureFeatures *ff, node *n, char *filename)
if (strcmp(feature, FUTURE_NESTED_SCOPES) == 0) {
ff->ff_nested_scopes = 1;
} else if (strcmp(feature, FUTURE_GENERATORS) == 0) {
- /* OK; this is processed by the parser */
+ ff->ff_generators= 1;
} else if (strcmp(feature, "braces") == 0) {
PyErr_SetString(PyExc_SyntaxError,
"not a chance");
@@ -233,6 +233,7 @@ PyNode_Future(node *n, char *filename)
ff->ff_found_docstring = 0;
ff->ff_last_lineno = -1;
ff->ff_nested_scopes = 0;
+ ff->ff_generators = 0;
if (future_parse(ff, n, filename) < 0) {
PyMem_Free((void *)ff);