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

[Chris Angelico]

On Mon, Sep 21, 2015 at 2:28 PM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
> Chris Barker wrote:
>>
>> It would be nice to have a:
>>
>> from __future__ import py3
>
>
> Or maybe
>
>   from __future__ import *
>
> should work?

Hah!

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 :)

ChrisA