21 Sep
2015
21 Sep
'15
1:08 p.m.
On Mon, Sep 21, 2015 at 02:21:21AM -0400, Random832 wrote:
Chris Angelico <rosuav@gmail.com> writes:
Even if it were made to work, though, it'd mean you suddenly and unexpectedly get backward-incompatible changes when you run your code on a new version. Effectively, that directive would say "hey, you know that __future__ feature, well, I'd rather just not bother - get the breakage right away". Kinda defeats the purpose :)
Yeah, well, that won't be a problem for this use case until Python 2.8 comes out.
There will not be an official Python 2.8. https://www.python.org/dev/peps/pep-0404/
Or do we expect *new* __future__ features to be added to maintenance releases of Python 2.7?
No. -- Steve