Tobias Oberstein
Hi all,
I'd like to ask if it would be appropriate and whether there is interest in making
"support Twisted on PyPy"
a project milestone for Twisted.
To a large extent, it is already supported (although not everything works yet. It has been deployed in production though (twistedmatrix.com is largely hosted on pypy+twisted).
I'd start contributing by setting up a buildslave for PyPy so that issues can be made transparent and identified and progress tracked.
Since PyPy is still very fast moving, that would need to be a beefy machine, since I would track PyPy trunk doing nightly PyPy builds and then use that for Twisted trials. It likely would involve stopping buildbot for the short period of PyPy installation, restarting it afterwards.
That would be useful. We currently do have a buildslave running tests against pypy, but we are looking at decomissioning it. The buildbot takes care of installing new versions of pypy (on a weekly basis). I'll need the follwing information from you (offlist): 1. Desired slave name. This will show up on http://buildbot.twistedmatrix.com/buildslaves 2. Password This is sent cleartext. 3. Email address This is used to send mail messages when the slave disappears. It isn't visible. 5. How many parallel builds you want allowed to run.
PS: The current trial results (Ubuntu 10.04 LTS i386, Twisted trunk, select reactor) ...
You should open tickets for these issues.