traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix bug that allowed future statements virtually anywhere in a module. 

If we exit via the break here, we need to set ff_last_lineno or
FUTURE_POSSIBLE() will remain true.  The bug affected statements
containing a variety of expressions, but not all expressions.  It has
been present since Python 2.2.
This commit is contained in:
Jeremy Hylton 2005-02-04 18:38:43 +00:00
parent 1f1d252f51
commit c9add9a483
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Python/future.c
View File

@ -93,7 +93,6 @@ future_parse(PyFutureFeatures *ff, node *n, const char *filename)
{
int i, r;
loop:
switch (TYPE(n)) {
case single_input:
@ -222,6 +221,7 @@ future_parse(PyFutureFeatures *ff, node *n, const char *filename)
n = CHILD(n, 0);
goto loop;
}
ff->ff_last_lineno = n->n_lineno;
break;
case atom:
@ -258,4 +258,3 @@ PyNode_Future(node *n, const char *filename)
}
return ff;
}