The problem, which they keep mentioning over and over, is that companies who actually donate have zero interest in a python 3 version. While they are a non profit, they have to pay the bills somehow.

Chicken and egg... But if there was good Python 3 support maybe more companies would contribute.

The value of PyPy is that it is a thing you can just drop in to make your code faster. If PyPy wants to gain any traction they pretty much have to concentrate on the version with the most existing code.

most of my existing production code is 3.4, hence my question.

I'm/we are also moving everything to 3.4, since we want all the nice things.

Python 3 is the future. There's a chance that when Pypy finally catches up with Python 2.7 (numpy, C extensions etc), it will be obsolete.

Python3 is a language. Python2 is also a language. Python3 might someday become wildly popular, but that doesn't magically make Python2 go away just because the name sounds the same.

From [PEP 373]:

> The End Of Life date (EOL, sunset date) for Python 2.7 has been moved five years into the future, to 2020. This decision was made to clarify the status of Python 2.7 and relieve worries for those users who cannot yet migrate to Python 3. See also PEP 466.

> This declaration does not guarantee that bugfix releases will be made on a regular basis, but it should enable volunteers who want to contribute bugfixes for Python 2.7 and it should satisfy vendors who still have to support Python 2 for years to come.

> There will be no Python 2.8 (see PEP 404).

Take note that the initial date was set to 2015 [2] and it was delayed only last year.

   [PEP 373]: http://legacy.python.org/dev/peps/pep-0373/
   [2]: https://hg.python.org/peps/rev/76d43e52d978

I too want 3.3+ support but I know some claim that there's very little demand from people actually doing something with PyPy for Python 3 support. I really think it may be a chicken and egg problem: that is, support will generate demand.

In any case the 3.3 branch seemed good when I compiled it last, it'd be nice to see a partial release.

"puhleeze give us Python 3...." repeated everywhere in this comment thread, yet the authors of pypy keep responding with the same line: pay some money and we'll do it. This speaks to what the real industry users of Python already know: 2.7 is where it's at, and they're prepared to pay for that, and not 3.x. Sure there'll be a bunch of people waving the 3 flag and saying "I use it" etc, but the bottom line is the bottom line: money. 2 attracts the dough.

If I were the PyPy guys I'd just announce that PyPy was now officially a fork of 2.7. This would bring all the numerical guys with them, all the corpos with big investments in 2 would fund them, and we could then let the 3.x zealots go off on their own tangent.

Anybody who likes what 3.x brings to the table should really spend a weekend learning Go, which does it all better, and faster.

I've been saying in these threads for ages that vectorization is the big win in Python (thank you PyPy), and not hobby projects like asyncio (miles better elsewhere), or (eyes rolling) type annotations.

Yes, this is one of those features that should be targeting the newest release, to provide a reason to upgrade, and not support lock-in to 2.7.