Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <rosuav@gmail.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.003
X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'explicitly': 0.04; 'subject:question': 0.08; '__future__': 0.09; 'broke': 0.09; 'sep': 0.09; '3.3,': 0.16; '9:20': 0.16; 'afterwards.': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'imo.': 0.16; 'mon,': 0.16; 'wrote:': 0.17; 'saying': 0.18; 'code.': 0.20; 'import': 0.21; 'received:209.85.214.174': 0.21; '3.x': 0.22; 'strip': 0.22; 'statement': 0.23; 'thus': 0.24; 'header:In-Reply-To:1': 0.25; 'supported': 0.26; 'am,': 0.27; 'guess': 0.27; 'message-id:@mail.gmail.com': 0.27; 'probably': 0.29; "i'm": 0.29; 'system,': 0.32; 'running': 0.32; 'to:addr :python-list': 0.33; 'received:google.com': 0.34; "won't": 0.35; 'received:209.85': 0.35; 'there': 0.35; 'but': 0.36; 'anything': 0.36; "i'll": 0.36; 'being': 0.37; 'ones': 0.37; 'quite': 0.37; 'received:209': 0.37; 'subject:: ': 0.38; 'to:addr:python.org': 0.39; 'received:209.85.214': 0.39; 'header:Received:5': 0.40; 'your': 0.60; 'risk': 0.66; 'finally': 0.66; 'guaranteed': 0.76
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Tj8mHsrgqvml8hnPQ2seqHv6MXYe0pe9z1E0hlRj3Ys=; b=uI8Btlk/EEKJss9KQm2WbnuVWpayeRltlccgKytvjhvRf1NHUqRG1uw7m/ODOGu3SL Neou29k8AenuYKBs6LkK/XHr+Nhy5L48I0UaVzISf9/T7yluWWyBVNvAGMrD6MSrVs5B OlAyVd1NPty/NNdXj04uLsLvBgKK1MavastOtLSUPWFz3onWOHwiN9v2j+cXkOqebyVO CVi0UOJ31GBCVTMLjT7zxj18UrcXEPxDk64Ftw1CnsvI+EI9q1AIdmj3FnXDI9AzG4Qr tCMgJm3lPghrf4HV54C2V9WBc84598Oki9i+d0PQhmNOt3iQFHgJ/DyijeNFQBhXtXzH +fJQ==
MIME-Version: 1.0
In-Reply-To: <63ca5a36-04d4-489a-b82e-9bb8e86bdc5e@v19g2000pbt.googlegroups.com>
References: <c9b2c268-fcc4-40f7-8769-517c13683894@v9g2000pbu.googlegroups.com> <mailman.96.1346608542.27098.python-list@python.org> <c989c63e-59da-410a-a89c-fcfccf92e8e3@q9g2000pbo.googlegroups.com> <mailman.116.1346618956.27098.python-list@python.org> <680feff1-8d8e-4f6d-8521-1e875479d1f7@k9g2000pbr.googlegroups.com> <mailman.118.1346622469.27098.python-list@python.org> <63ca5a36-04d4-489a-b82e-9bb8e86bdc5e@v19g2000pbt.googlegroups.com>
Date: Mon, 3 Sep 2012 09:28:17 +1000
Subject: Re: newbie ``print`` question
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.120.1346628500.27098.python-list@python.org>
Lines: 20
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1346628500 news.xs4all.nl 6904 [2001:888:2000:d::a6]:42607
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:28327

On Mon, Sep 3, 2012 at 9:20 AM, gwhite <gwhite@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