The first stable release of PyPy3
morepypy.blogspot.com
The first stable release of PyPy3
1–10 of 92 posts
Re: The first stable release of PyPy3
#2Thank you.
Re: The first stable release of PyPy3
#3I wish the community would just switch entirely to pypy. Being able to just slightly performance sensitive code in python is a huge win.
Re: The first stable release of PyPy3
#4Wow, this is a very exciting moment for the Python world.
And they didn't even reached their funding goal for "py3k in pypy" [1]. This is dedication. I encourage everyone to fund this extremely incredible project!
Re: The first stable release of PyPy3
#5This is awesome, now just to wait for a Python 3.4 PyPy release :D
Re: The first stable release of PyPy3
#6I wish the community would just switch entirely to pypy. Being able to just slightly performance sensitive code in python is a huge win.
> I wish the community would just switch entirely to pypy.
What purpose would that serve?
> Being able to just slightly performance sensitive code in python is a huge win.
I think you slightly this phrase, but aside from that pypy does not work for everybody and everything (e.g. at best it's no slower for sphinx, it really doesn't like the way docutils works). It's not like pypy's a magic wand.
Re: The first stable release of PyPy3
#7This is awesome, now just to wait for a Python 3.4 PyPy release :D
And Numpy! And ctypes (for Matplotlib)!
Although I must say, numpypy is quite usable already!
Re: The first stable release of PyPy3
#8Excellent. I've been waiting for this for a long time.
Re: The first stable release of PyPy3
#9I don't know or use Python but why an implementation that is trying to be "superior" still has the GIL?
Re: The first stable release of PyPy3
#10I don't know or use Python but why an implementation that is trying to be "superior" still has the GIL?
This donation page has some background on how PyPy is proposing to replace the GIL with software transactional memory: