On Sun, Jan 19, 2014 at 4:06 PM, Steven D'Aprano <steve@pearwood.info> wrote:
On Sun, Jan 19, 2014 at 03:44:32PM -0800, Ethan Furman wrote:
> On 01/19/2014 03:35 PM, Ben Finney wrote:
> >
> >In other words, those who want Python 2 to continue need to either bite
> >the bullet and move their migration to Python 3 forward
> Um, if they want Python 2 to continue, why would they migrate to Python 3?

Because you can't always get what you want. I want a pony, but since I
can't afford one or have any place to keep it, I've made do without.

I think the odds of Python getting

        from __future__ import pony

are slightly higher than there being a Python 2.8. I assume by "pony" you really mean what I'd like to have:

        from __future__ import everything

since my goal is to write Python 3 compatible code even though I'm temporarily stuck with Python 2 due to stack issues. The __future__ imports makes it easier to write forward compatible code. As it is, I have to list the individual imports in every file and I also add:

        range = xrange

--- Bruce