[pypy-dev] Is cpyext dead forever?

Maciej Fijalkowski fijall at gmail.com
Sat May 18 21:57:13 CEST 2013

On Sat, May 18, 2013 at 9:49 PM, Matti Picus <matti.picus at gmail.com> wrote:
> On 18/05/2013 10:45 PM, Maciej Fijalkowski wrote:
> On Sat, May 18, 2013 at 8:51 PM, Matti Picus <matti.picus at gmail.com> wrote:
> cpyext is currently disabled on default. Is there a branch to revive it?
> Or are we expecting cffi to replace all interaction with external c code?
> I'm not sure what will be more painful, getting the world to rewrite all
> modules or supporting cpyext, both seem non-trivial.
> (I'm opening the discussion here since I'm not sure if everyone was heard in
> the discussion on IRC)
> Matti
> It's disabled because I broke it. I'll unbreak it some time soon, it's
> just that issue is involved. I'm sorry about that, but there was no
> goal to deprecate it any time soon.
> Cheers,
> fijal
> thanks, no hurry, I just misunderstood.
> Matti

In a way it should not have happened at all. But also in a way I would
argue cpyext is broken (annotation-wise) and my changes merely exposed
brokenness. It's still my duty to fix it though ;-)


More information about the pypy-dev mailing list