RetroSearch Browse

Sat Feb 5 07:44:32 CET 2005 · https://mail.python.org/pipermail/python-dev/2005-February/051430.html

On Saturday 05 February 2005 05:38, jhylton at users.sourceforge.net wrote:
> 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.

While this is undoubtedly a bug fix, I'm not sure that it should be 
backported - it will break people's code that is "working" now (albeit
in a faulty way). What do people think?

-- 
Anthony Baxter     <anthony at interlink.com.au>
It's never too late to have a happy childhood.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-February/051430.html below:

[Python-checkins] python/dist/src/Python future.c, 2.14, 2.15