In light of this feedback from the PyPy dev team, is there any ongoing work on a cffi version of lxml? I know there is a github repo here ( https://github.com/amauryfa/lxml/tree/cffi) that lists PyPy 2.4 support, but it shows no activity in the last year so I'm guessing it's dormant. Thanks, - Jeff ---------- Forwarded message ---------- From: Armin Rigo <arigo@tunes.org> Date: Wed, Nov 4, 2015 at 5:09 AM Subject: Re: [pypy-dev] Looking for clues to consistent Seg Fault in PyPy 2.6.1 To: Jeff Doran <jdoran@lexmachina.com> Cc: Amaury Forgeot d'Arc <amauryfa@gmail.com>, PyPy Developer Mailing List < pypy-dev@python.org>, lxml@lxml.de Hi Jeff, On Tue, Nov 3, 2015 at 11:57 PM, Jeff Doran <jdoran@lexmachina.com> wrote:

Just an update on this problem. I retested using the latest lxml source from here ( 3.5.0b2?)

There were a few fixes to PyPy's cpyext layer. But there was no change to lxml itself. That means it is still using a broken approach to work around a CPython C API difference. Namely, this is the weakref stuff which is done incorrectly---although I don't know how to do that correctly. For now, lxml (the non-cffi version) is not compatible with PyPy at all. A bientôt, Armin.