[Python-ideas] add a single __future__ for py3?

Random832 random832 at fastmail.com
Mon Sep 21 08:21:21 CEST 2015

Chris Angelico <rosuav at 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. Or do we expect *new* __future__ features to be added to
maintenance releases of Python 2.7?

More information about the Python-ideas mailing list