Amaury Forgeot d'Arc <amaur...@gmail.com> added the comment:
The code is excluded from compilation with a
#ifdef PY_PARSER_REQUIRES_FUTURE_KEYWORD
There is no __future__ feature in 3.0 for the moment, but the code stays
here as a placeholder, to remind developers what they need to do to
support __future__ flags that change the behavior of the lexer.
----------
nosy: +amaury.forgeotdarc
resolution: -> invalid
status: open -> closed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue4866>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
