Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!eternal-september.org!feeder.eternal-september.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!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.005
X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'operator': 0.03; 'subject:Python': 0.06; 'differently': 0.07; 'string': 0.09; 'created,': 0.09; 'cc:addr:python-list': 0.11; 'jan': 0.12; '"from': 0.16; '__future__': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'magic': 0.16; '(you': 0.16; 'wrote:': 0.18; 'module': 0.19; 'settings': 0.22; 'example': 0.22; 'import': 0.22; 'cc:addr:python.org': 0.22; 'module,': 0.24; 'decide': 0.24; 'cc:2**0': 0.24; 'source': 0.25; 'define': 0.26; 'header:In-Reply-To:1': 0.27; 'feature': 0.29; 'message- id:@mail.gmail.com': 0.30; 'code': 0.31; 'though.': 0.31; 'maybe': 0.34; 'subject:the': 0.34; "can't": 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'really': 0.36; 'changing': 0.37; 'easily': 0.37; 'starting': 0.37; 'issue': 0.38; 'pm,': 0.38; 'rather': 0.38; 'future': 0.60; 'worry': 0.60; 'break': 0.61; "you're": 0.61; 'effectively': 0.66; 'benefit': 0.68; '("this': 0.84; 'to:none': 0.92
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:cc :content-type; bh=14Eh5mfTVqX7ltN2LxIabq3sGZS2pvynmlcnEI7II3A=; b=rdsFp+ILI2JaLE2r5U/v/Jpyu1zP6x0PMZQmPcScwuah+anyiejXMWlArjgwZQt9gO esAoIdiwBMv2U5VTlqGL0SjYyOevTvS9hsRqoxV8Q2Y7UcjmGyk0w/0tuMZrShCQVucE 0lAj9/mOfsUwnfeVYa5LG6UPX2rAhxF/gy8yIkW1VrJZTYQ2hvxe1LugfQgL9LEhJM+3 hlK+KKxzPmuuXi1M5bbABPdMcYatE3/4x1XKSKWXjJZibdxGAbsMX0d9PJcrDCMvd8Rm Ql0G8fbN4beUUGDGkhaJCyZDblROrv4RS6N0lE5H3uv5ZXNeani3kPdgkK0GgExH5h20 jnBA==
MIME-Version: 1.0
X-Received: by 10.68.133.6 with SMTP id oy6mr11833900pbb.153.1389060059552; Mon, 06 Jan 2014 18:00:59 -0800 (PST)
In-Reply-To: <CABicbJ+YMRLHqQQ3nFLeqqxnvqRLRioZc9X3pZUMfZWzgEbMSw@mail.gmail.com>
References: <laf00q$10k$1@ger.gmane.org> <CAPTjJmqzc2AQJ6TrBtCFnT+NBp8uYWMxMhtGNpLr+NGyhoxO-g@mail.gmail.com> <CABicbJ+k9Yim879QaDtty_dNvpZMgKA8W-zX6Xcsc5BQcnaCaQ@mail.gmail.com> <CAPTjJmozt8XcWrW2xAX7oeHDQHcDDWkoY7kMK0YXdYU+z+cOfQ@mail.gmail.com> <CABicbJ+YMRLHqQQ3nFLeqqxnvqRLRioZc9X3pZUMfZWzgEbMSw@mail.gmail.com>
Date: Tue, 7 Jan 2014 13:00:59 +1100
Subject: Re: the Gravity of Python 2
From: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
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: <https://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: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.5106.1389060068.18130.python-list@python.org>
Lines: 19
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1389060069 news.xs4all.nl 2852 [2001:888:2000:d::a6]:52362
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:63395

On Tue, Jan 7, 2014 at 12:55 PM, Devin Jeanpierre
<jeanpierreda@gmail.com> wrote:
> What if we decide there is no single source of responsibility, and it
> can't be limited exactly to a module, and make a __future__ feature
> the best we can regardless? We can still exact some benefit from a
> "sloppy" __future__ feature: we can still move code piecemeal.

I worry that it's starting to get into the realm of magic, though.
Maybe dict.keys() isn't the best example (you can easily make your
code 2+3 compat by just calling list() on it immediately, which is
effectively "from __past__ import absence_of_views"), but the issue is
the same with string autoencodings. It's really hard to define that
the + operator will do magic differently based on a future directive,
and changing the object ("this string will not autoencode") means
you're not tweaking things per-module, and behaviour will change
and/or break based on where some object was created, rather than the
settings on the module with the code in it.

ChrisA