Hi, On Nov 20, 2007 9:50 PM, Christian Tismer <[EMAIL PROTECTED]> wrote: [snip]
I agree that there are many ways in which PyPy could be interesting for production use, not just a high-performance full-fledged Python interpreter. I've been asking about the interpreter as I got the strong impression that this was the main aim of the project when I asked about this kind of stuff at EuroPython. As an example, I think running this interpreter on, say, the, JVM, could be quite interesting, given its compliance with the language, and if it exposes Java libraries. > There are already many people interested in what PyPy can do > today, and I want to call this being successful right now. Some people were quite interested in the CPython extension language system. That has been in limbo for half a year, and the project just told us that people can add it back with the new system if they should have such a desire. That's what prompted me to speak up about the perceptions this project may have. If you want to get interested people to contribute, you'll need to offer features that in some way compete successfully with other systems. On the extension mechanism front, you won't compete with Pyrex/Cython or CTypes right now. Theoretically PyPy could come up with something nicer than Pyrex, but in practice one would need to invest a lot of time to make it work first. There's no interest from the project itself to invest significant time on it. Building interpreters is more important. On the interpreter front however, I've gotten a worryingly familiar lack of concreteness and unwillingness to promise anything. I'd suggest the project get more concrete and sets some targets. Once you do that, you might get more people willing to help. Regards, Martijn _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
