This 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!
PyPy has had ctypes support for a great long while.
The first stable release of PyPy3
51–60 of 92 posts
Re: The first stable release of PyPy3
#52Earlier quoted context omitted.
> 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.
> What purpose would that serve? If PyPy became the official/canonical implementation, PyPy would receive more attention and third-party library compatibility would be a requirement. Complaints about Python's slowness would be somewhat less relevant, and Python might see wider adoption. The RPython toolchain would receive more attention and that could be useful to other languages. There are plenty of reasons, but PyP…
I agree with you, but it will never happen. GvR wants a as-simple-as-possible reference implementation, for one, he has to maintain it with a volunteer dev team. Also, there's a split in the Python community between guys like me and you- and the scientific squad. Until the scientific stuff works 100% in PyPy you'd lose a significant portion of the Python userbase by dumping CPython.
GvR has done enough damage to Python with Python3. I don't intend to encourage him to do make any more changes. Us Python web developers are better off using what we have (non reference implementations, which don't hurt anyone), or just use Node.js.
Re: The first stable release of PyPy3
#53Earlier quoted context omitted.
> Building for i386 at some point requires running a bootstrap process that doesn't fit in memory. Seriously, it takes more than 4gigs to build PyPy? Is that also necessary for other platforms besides OpenBSD?
4GB is literally nothing. My laptop has 16, most servers I use have 128+. 4GB is netbook territory.
... I think the implication is that more than 4GB would exceed the pre-[PAE][1] memory limit[2]. A form of cross-compilation might work, though PyPy build isn't exactly a simple, 'classical' build process. :P
Edit: also, looking at your comments[3E] it looks like surely you know this (sorry) so I'm now really not sure what you're getting at... :P
[1]: http://en.wikipedia.org/wiki/Physical_Address_Extension
[2]: and even with PAE you still need to split into multiple processes/address spaces to do anything useful
Re: The first stable release of PyPy3
#54Re: The first stable release of PyPy3
#55Re: The first stable release of PyPy3
#56Earlier quoted context omitted.
PyPy seems to be 7x faster!
On a silly piece of code that nobody would ever have any use for. I have tried PyPy for "real" data and numerical tasks from time to time, and never have I noticed any sort of speedup. Usually it's slower than CPython. Perhaps this latest version will be different, who knows.
I'm using it in production, and speedups tend to be on the order of 4-5x for my app (the compute-intensive part involves hierarchical agglomerative clustering of documents by text similarity, so it's data/numbers-heavy). Obviously it'll depend on your individual application (and non-CPU-bound tasks won't benefit much), but we switched to PyPy because it showed major improvements in profiling of our app on production data (and we switched around PyPy's 1.9 release, so it's even better now). It's not like everyone's just imagining the speed improvements...
Re: The first stable release of PyPy3
#57Earlier quoted context omitted.
> Building for i386 at some point requires running a bootstrap process that doesn't fit in memory. Seriously, it takes more than 4gigs to build PyPy? Is that also necessary for other platforms besides OpenBSD?
4GB is literally nothing. My laptop has 16, most servers I use have 128+. 4GB is netbook territory.
4GB is not literally nothing, it's 25% of the memory available on your laptop. That's a significant chunk.
Re: The first stable release of PyPy3
#58I wish the community would just switch entirely to pypy. Being able to just slightly performance sensitive code in python is a huge win.
Maybe moving libraries & code to Python 3 should be the priority.
Convincing distros to package it as the default "python" should be the priority. Until that happens, Python 3 will see limited adoption. The path of least resistance will always have the most traffic.
Re: The first stable release of PyPy3
#59Re: The first stable release of PyPy3
#60Earlier quoted context omitted.
> Building for i386 at some point requires running a bootstrap process that doesn't fit in memory. Seriously, it takes more than 4gigs to build PyPy? Is that also necessary for other platforms besides OpenBSD?
4GB is literally nothing. My laptop has 16, most servers I use have 128+. 4GB is netbook territory.
That's not true. $1000 ultrabooks often have 4GB. Hell, the base model rMBP has 4GB (I paid the extra for 8GB).