No other python implementation can convert python programs to executables.
There's shedskin, which is actually very good as these things go:
http://code.google.com/p/shedskin/
Like RPython, you have to write in a small subset of python which can
be a little frustrating once you've gotten used
/lurk
A while back I noticed that some math-related rpython-produced C was much
slower than it should have been. After I figured out what was going on, I
set it aside, but I see someone mentioned doing some numpy stuff on IRC
today so I dug up the tests.
Note that the following slowdown
cfb wrote:
I thought I would start a new thread for discussing what PyPy needs to
become production ready (whatever that is) and succeed as a Python
implementation.
[...]
- Speed. The JIT is still not in a state where it really speeds up
arbitrary Python code. I expect this to change
While I'm waiting to hear back on the bug tracker about whether some odd
binascii behaviour is intentional, I was doing some reading. Some of the
work by these guys
http://www.cs.washington.edu/research/progsys/wasp/wasp.html
is very interesting, especially their latest
Automated Soundness
