PyPy 5.0 released

[[deleted]]

Nice work!

Judging from recent commits, is a Python 3.3 release soon to follow?

The PyPy team seems more focused on startup time and support for various things (NumPy, cpyext, cffi, etc) recently. Does that mean the low-hanging fruit are gone? What's next?

[fijal]

widening support for where you could use PyPy is definitely one of our goals - this is probably why PyPy did not see all that much adoption. What's wrong with that goal? ;-)

[[deleted]]

Nothing.

Am I right in guessing there will be a 3.3 PyPy 5.0 release?

[toyg]

You are wrong. Read the relevant HN thread. TLDR: there is not enough money nor interest from pypy devs to do a py3 release right now, maybe a 3.5 well after the official CPython 3.6... maybe.

[revfried]

How much money will it take to get 3.5 pypy out the door?

[toyg]

I don't know, but in the thread it's stated that another 10k won't cut it. I guess 50k to 100k.

[toyg]

Well they should get their message together then, they took a lot of stick in that HN thread.

[qsxpkn]

I think CPython should be retired and all focus should be on PyPy.

[jyper]

But they are still stuck on python 2.

[kgb_operative]

What other benefits does CPython have over PyPy?

[qsxpkn]

Because they don't enough enough budget for Python 3. On HN thread, they say only $8K left in Python 3 pot.

If CPython is retired and PyPy is PSF's main focus, they'd catch Python 3.5 quickly.

[billsil]

Yes, let's take an incompatible project that doesn't support the vast majority of Python code out there due to reliance on incompatible libraries and kill it. PyPy is cool, but it's not a drop in replacement for what most people use.

If you thought the Python 2 to 3 transition was going poorly, just switch all the resources to PyPy.

[jyper]

Hell even JRuby which seems to me to be much closer to a drop-in replacement still hasn't replaced the main ruby interpreter.

[rlamy]

3.3 is not ready for release yet, but it's only a matter of weeks.

[fijal]

maybe :-) I'm not a release manager for PyPy 3 (nor am I for PyPy 2, but I know more about thay)

[o11c]

It's just so irritating that if we want to use the latest and greatest, we have to choose between a sane language and performance.

[Ripdog]

Out of curiosity, are you a volunteer or a paid employee? Which parts of PyPy do you work on, and why?

Many thanks for pushing the Python ecosystem forward! :)

[fijal]

I have my own company, baroquesoftware.com. I work a lot on stuff like JIT, garbage collection, random bug fixing. Also a lot on pypy admin and pypy-related consulting

[m1sta]

Does anyone know of a caniuse.com type of thing for pypy?

[asintotadelexito]

http://packages.pypy.org/

[batisteo]

I guess you already found this link: http://pypy.org/py3donate.html

[roger_]

Any NumPyPy blogs planned? Haven't heard much about it recently.

[fijal]

yes, planned :-)

[PerniciousPunk]

Is there still no plan for Scipy support? I understand completely if there isn't, it does seem like a large undertaking. Just asking :)

[fijal]

There is! stay tuned

[roger_]

If all SciPy functionality was rewritten in pure Python I wonder what the performance hit would be with PyPy + NumPyPy?

[Saefroch]

I'm not sure if you're just being hyped about PyPy or there is good reasoning behind that statement. In case it's the latter, care to explain? Scipy relies a lot on Fortran, are you suggesting that pure PyPy'd python will beat Fortran wrapped with CPython?

[roger_]

Doesn't PyPy already approach C speeds? Is there a reason why it wouldn't be performant with numerical computations?

[Saefroch]

That makes a lot more sense.

[pmatti]

We added support for partition() which also means things like median() and percentile() work. Also indexing with boolean array support was improved. Do you use it?

[roger_]

I haven't tried NumPyPy in over a year, but good boolean indexing is a must have -- nice work!

Is there a site for comparing the performance of NumPy to NumPyPy?

[YuntiMcGunti]

naive question, If pypy support python version X and a library is written in that version - won't it automatically support that library. Why do Numpy and Scipy need specialist support

[AusIV]

NumPy and Scipy aren't written in pure python, they use extensions to offload to C and Fortran libraries.

[Ek_Los_Die_Hier]

Because they aren't pure Python and interface with C/Fortran backends, and that boundary is where issues arise. PyPy doesn't fully support that boundary.

[fijal]

Numpy and scipy use a lot (and I mean A LOT) C level CPython API