diff options
| author | Tim Peters <tim.peters@gmail.com> | 2001-07-16 02:29:45 +0000 |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2001-07-16 02:29:45 +0000 |
| commit | 0bfd3b1baa5c5cfbcc6d35622f6f2781d4e4c9d8 (patch) | |
| tree | e7cdd6a0194a21f09df9f9377fccd9d8865c8f75 /Python/future.c | |
| parent | 58b7b5b9b28ce995f30c3d38464bc146f5c66869 (diff) | |
| download | cpython-0bfd3b1baa5c5cfbcc6d35622f6f2781d4e4c9d8.tar.gz | |
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.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Python/future.c b/Python/future.c index 70be26b548..f0960ae861 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); |