newbie ``print`` question

[Chris Angelico]

On Mon, Sep 3, 2012 at 9:20 AM, gwhite <gwhite at ti.com> wrote:
> I guess you're saying 3.x will just ignore:
>
> from __future__ import print_function
>
> I'll risk being silly, and thus ask: but what if when I get to 3.x
> there is no __future__, as it is now "present?"  Do I need to strip
> out the line?
>
> What would happen when I finally started running 3.3, and a new
> __future__ was made that broke the old syntax?  Do I need to strip out
> the line?
>
> I'm probably over thinking it.  I don't know what I am doing.  lol!

The __future__ statement is guaranteed to be supported forever
afterwards. And new ones won't do anything unless you explicitly put
them into your code. It's quite a good system, imo.

ChrisA