This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2009年01月07日 14:04 by ganderson, last changed 2022年04月11日 14:56 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg79332 - (view) | Author: (ganderson) | Date: 2009年01月07日 14:06 | |
At the lines 99 .. 103, there are the message on Python 2.6. |
|||
| msg79333 - (view) | Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * (Python committer) | Date: 2009年01月07日 14:37 | |
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. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:56:43 | admin | set | github: 49116 |
| 2009年01月07日 14:37:22 | amaury.forgeotdarc | set | status: open -> closed resolution: not a bug messages: + msg79333 nosy: + amaury.forgeotdarc |
| 2009年01月07日 14:06:49 | ganderson | set | messages: + msg79332 |
| 2009年01月07日 14:04:40 | ganderson | create | |