tree 7d53f1d02fdcc9f6ce4bd1e5130ba1f57269bb3f
parent 4dbf87152eb69e8c8c87d3081630c4bc02d7cace
author Tim Peters <tim.peters@gmail.com> 995250585 +0000
committer Tim Peters <tim.peters@gmail.com> 995250585 +0000
HG:extra convert_revision:svn%3A6015fed2-1504-0410-9fe1-9d1591cc4771/python/branches/legacy-trunk%4021772

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.