commit | 5ba58662817b708a453020f0425fe4747ea6d5cb | [log] [tgz] |
---|---|---|
author | Tim Peters <tim.peters@gmail.com> | Mon Jul 16 02:29:45 2001 +0000 |
committer | Tim Peters <tim.peters@gmail.com> | Mon Jul 16 02:29:45 2001 +0000 |
tree | 7d53f1d02fdcc9f6ce4bd1e5130ba1f57269bb3f | |
parent | 4dbf87152eb69e8c8c87d3081630c4bc02d7cace [diff] |
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.