[pypy-dev] pypy on Tim Bray's blog

[Maciej Fijalkowski]

>
> Martijn Faassen wrote:
> [snip]
>  > Again, I'm not trying to criticize what the project has already done.
>  > I'm trying to be a voice of pragmatism and the voice of a potential
> open
>  > source end-user. Listen to me if you like; it's not an enemy voice.
>  > There are two PyPy technologies that I can see that are close to
>  > pragmatic fruition now:
>  >
>  > * writing CPython modules in RPython (I completely lost track of what
>  > the state of this is since there have been a lot of changes)
>
> It's still working but mostly accidentally. It needs some rethinking and
> a rewrite. We have now better machinery and also ideas how to make it
> really fast, but it's a manpower problem.  There isn't anyone interested
> enough in supporting this in the current PyPy team. If somebody outside
> the current PyPy-team really wanted this and were willing to work on it
> we (or at least me personally) would give him all the support we can.


Me as well. The thing is that extcompiler is keeping alive a lot of code
which we don't need otherwise. I would be more than happy to help someone
reimplement it (shouldn't be a hard task anyway, our machinery is better
suited by now). I can even imagine doing that for money. But I'm not willing
to spend my free time on that (besides helping someone, which always goes
into an account). The main reason is that we really don't want to fork our
efforts into too many directions. Also note that while this might be a good
idea, you still end up with RPython, which is nice, cool, better than pyrex
or C, but for example error reporting is somewhat not-as-good-as-possible.
We're trying to improve it anyway, but making extcompiler nice cool tool
would need some external will.

Cheers,
fijal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20071114/1e899957/attachment.html>