Comments on: Attacking PyPy http://www.philhassey.com/blog/2007/11/30/attacking-pypy/ game dev blog Fri, 06 Jan 2012 23:00:54 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: philhassey http://www.philhassey.com/blog/2007/11/30/attacking-pypy/comment-page-1/#comment-217 philhassey Sat, 01 Dec 2007 22:54:34 +0000 http://www.philhassey.com/blog/2007/11/30/attacking-pypy/#comment-217 Chris - shed-skin only translates programs that are written in it's version of Rpython. Both PyPy's Rpython and shed-skin's Rpython support roughly the same sub-set python. The notable difference between the code outputted is: shed-skin produces human readable C++ code (with C++ classes, namespaces, etc) PyPy produces (fairly) unreadable C code. Phil Chris –

shed-skin only translates programs that are written in it’s version of Rpython. Both PyPy’s Rpython and shed-skin’s Rpython support roughly the same sub-set python.

The notable difference between the code outputted is:

shed-skin produces human readable C++ code (with C++ classes, namespaces, etc)
PyPy produces (fairly) unreadable C code.

Phil

]]> By: Christopher Armstrong http://www.philhassey.com/blog/2007/11/30/attacking-pypy/comment-page-1/#comment-216 Christopher Armstrong Sat, 01 Dec 2007 22:18:41 +0000 http://www.philhassey.com/blog/2007/11/30/attacking-pypy/#comment-216 There's a major difference: ShedSkin is a general Python to C++ translator. PyPy's translator translated your *R*Python to C. ShedSkin has to do a lot more work to make sure that it supports all the dynamism of Python, whereas the C backend just needs to support the very non-dynamic RPython. There’s a major difference: ShedSkin is a general Python to C++ translator. PyPy’s translator translated your *R*Python to C. ShedSkin has to do a lot more work to make sure that it supports all the dynamism of Python, whereas the C backend just needs to support the very non-dynamic RPython.

]]> By: philhassey http://www.philhassey.com/blog/2007/11/30/attacking-pypy/comment-page-1/#comment-215 philhassey Sat, 01 Dec 2007 17:28:38 +0000 http://www.philhassey.com/blog/2007/11/30/attacking-pypy/#comment-215 Nothing comes to mind other than C vs C++ overhead. Nothing comes to mind other than C vs C++ overhead.

]]> By: Mark Dufour http://www.philhassey.com/blog/2007/11/30/attacking-pypy/comment-page-1/#comment-212 Mark Dufour Sat, 01 Dec 2007 11:18:41 +0000 http://www.philhassey.com/blog/2007/11/30/attacking-pypy/#comment-212 hi phil, any idea where the 30% difference stems from? possibly something minor I might fix? mark dufour. hi phil,

any idea where the 30% difference stems from? possibly something minor I might fix?

mark dufour.

]]> By: philhassey http://www.philhassey.com/blog/2007/11/30/attacking-pypy/comment-page-1/#comment-210 philhassey Fri, 30 Nov 2007 16:09:55 +0000 http://www.philhassey.com/blog/2007/11/30/attacking-pypy/#comment-210 Markus: Actually - you've got to consider all the SDL binding stuff too .. I did this ages ago, but thanks for the reminder - I think I'll check pyrex out again and see how it suits me. Maybe I'll do an article about that next :) Carl: Yeah, by PyPy I meant Rpython. Feel free to do whatever you like with the contents of that .zip file. public domain as far as I'm concerned. You couldn't use ShedSkin's FFI on top of CPython .. ShedSkin's FFI is literally C++ with a few helper classes + you have to write a bit of dummy code in python demonstrating how the functions will be used. You don't actually have to write any ctypes / rffi -esque stuff. (Check out my example lib/_gfx.* from my previous post to see what it looks like.) Markus:
Actually – you’ve got to consider all the SDL binding stuff too .. I did this ages ago, but thanks for the reminder – I think I’ll check pyrex out again and see how it suits me. Maybe I’ll do an article about that next :)

Carl:
Yeah, by PyPy I meant Rpython. Feel free to do whatever you like with the contents of that .zip file. public domain as far as I’m concerned.

You couldn’t use ShedSkin’s FFI on top of CPython .. ShedSkin’s FFI is literally C++ with a few helper classes + you have to write a bit of dummy code in python demonstrating how the functions will be used. You don’t actually have to write any ctypes / rffi -esque stuff. (Check out my example lib/_gfx.* from my previous post to see what it looks like.)

]]> By: Carl Friedrich Bolz http://www.philhassey.com/blog/2007/11/30/attacking-pypy/comment-page-1/#comment-209 Carl Friedrich Bolz Fri, 30 Nov 2007 14:57:37 +0000 http://www.philhassey.com/blog/2007/11/30/attacking-pypy/#comment-209 Yay, that is extremely cool! We should steal that SDL wrapper :-). Can you test ShedSkin's FFI on top of CPython without translating the program first? Yay, that is extremely cool! We should steal that SDL wrapper :-) . Can you test ShedSkin’s FFI on top of CPython without translating the program first?

]]> By: Markus Gritsch http://www.philhassey.com/blog/2007/11/30/attacking-pypy/comment-page-1/#comment-205 Markus Gritsch Fri, 30 Nov 2007 13:53:30 +0000 http://www.philhassey.com/blog/2007/11/30/attacking-pypy/#comment-205 Nice posts. To make the list (ShedSkin, PyPy) complete, you can also use Pyrex (http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/) to build amazingly fast extension modules. Some time ago I also played around with some Mandelbrot examples. Here is the Pyrex code for the inner loop: def performIterations (double p_a, double p_b, long p_max): cdef double r, i, x, y, d r = i = x = y = d = 0.0 cdef long n n = 0 while d < 4.0 and n < p_max: x = r; y = i; r = x * x - y * y + p_a i = 2 * x * y + p_b d = r * r + i * i n = n + 1 return n The advantage is, that Pyrex compiles the above code to C-Code, which can then be compiled to a .pyd. On Windows for example, the size of this .pyd is only 8 kB. No other library is needed in contrast to ShedSkin. Nice posts. To make the list (ShedSkin, PyPy) complete, you can also use Pyrex (http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/) to build amazingly fast extension modules. Some time ago I also played around with some Mandelbrot examples. Here is the Pyrex code for the inner loop:

def performIterations (double p_a, double p_b, long p_max):
cdef double r, i, x, y, d
r = i = x = y = d = 0.0
cdef long n
n = 0
while d < 4.0 and n < p_max:
x = r; y = i;
r = x * x – y * y + p_a
i = 2 * x * y + p_b
d = r * r + i * i
n = n + 1
return n

The advantage is, that Pyrex compiles the above code to C-Code, which can then be compiled to a .pyd. On Windows for example, the size of this .pyd is only 8 kB. No other library is needed in contrast to ShedSkin.

]]> By: xtian http://www.philhassey.com/blog/2007/11/30/attacking-pypy/comment-page-1/#comment-203 xtian Fri, 30 Nov 2007 07:22:02 +0000 http://www.philhassey.com/blog/2007/11/30/attacking-pypy/#comment-203 Cool! When you say "implemented in PyPy", do you mean you implemented it in RPython? Cool!

When you say “implemented in PyPy”, do you mean you implemented it in RPython?

]]>