On Sat, Nov 21, 2009 at 3:05 PM, Maciej Fijalkowski <fijall@gmail.com> wrote:

No, noone did. You can't get C module to work on PyPy, you need to port it to RPython first. I'm not aware about anyone who would like to work on it among core devs, I suppose feel free to do so, we can help. It's open source after all :-)

Cheers, fijal

Oh, and by the way, personally I would prefer to kill the GIL, so we don't have to worry any more (but also noone from core devs is working on it). Cheers, fijal

On Sat, 2009-11-21 at 09:35 -0500, Gary Robinson wrote:

OK, thanks for the confirmation that it's not working yet, and letting me know what it would take!

I wish we had the resources to take on the task of converting it to RPython, but there's no way at this point. :) I'm using pyprocessing with unladen swallow now and it works fine but for the kinds of things we're doing (mathy floating point stuff) I'd expect more speed from PyPy...

The C component of multiprocessing, at least in python 2.6 is tiny and trivial: a read and write implementation for the underlying connection class. It would probably be better off converted to plain python for pypy in any case. On Sat, 2009-11-21 at 15:06 +0100, Maciej Fijalkowski wrote:

Oh, and by the way, personally I would prefer to kill the GIL, so we don't have to worry any more (but also noone from core devs is working on it).

What, roughly, would be required to remove pypy's gil? I have heard rather nebulous tales of woe and tribulation on the cpython lists referring to fine-grained per-object locking, re-entrant garbage collectors, abi stability, and other horrors. I have no idea what bits of this dubious information would be relevant to pypy's rather more abstract internals, however. -Terrence

We don't support Python 2.6, and probably won't for at least a year.

pyprocessing is the module that multiprocessing sprang from. pyprocessing is much older, and works fine with python 2.5. (2.6's multiprocessing module has been backported to 2.5 too, I hear, but I'm not using it.) pyprocessing is here: http://pyprocessing.berlios.de/. (The actual module is called "processing" but pyprocessing has long been the name people have used to refer to it.) If somebody got that working, it should be a relatively short step to get multiprocessing working in PyPy's 2.6-compatible version. I care far more about pyprocessing than about 2.6... If the PyPy GIL was gone, that would be better of course, but that doesn't sound like it's going to happen any time soon... -- Gary Robinson CTO Emergent Music, LLC grobinson@flyfi.com 207-942-3463 Company: http://www.flyfi.com Blog: http://www.garyrobinson.net On Sat, 21 Nov 2009 08:05:52 -0600, Benjamin Peterson wrote:

2009/11/21 Gary Robinson <grobinson@flyfi.com>:

...

Hi,

I'm wondering whether anyone has gotten the pyprocessing/multiprocessing module (in one version or the other) working with PyPy? I don't see it listed among the supported modules, but I want to ask to make sure I'm not just missing something. If it's not working yet, is there an ETA??

We don't support Python 2.6, and probably won't for at least a year.