[issue21591] "exec(a, b, c)" not the same as "exec a in b, c" in nested functions
Nick Coghlan
report at bugs.python.org
Sun Aug 10 01:58:18 CEST 2014
Nick Coghlan added the comment:
Agreed reverting isn't necessary - main thing is to figure out what went wrong in the py test suite and come up with a new test case that covers it.
The reason I suspect it's the missing runtime check that's causing the py problem is because (as far as I am aware), Jinja2 generates AST constructs directly and compiles those, and thus may be relying on the runtime check. It's just a theory, though.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21591>
_______________________________________
More information about the Python-bugs-list
mailing list