[pypy-dev] 5.1 has been released

[Phyo Arkar]

I would like to help , i can get Two Interns who love python a lot . But
cpyext needs C skills , right?

On Fri, Apr 22, 2016 at 11:34 AM Matti Picus <matti.picus at gmail.com> wrote:

> On 22/04/16 07:02, Phyo Arkar wrote:
> > Congrats PyPy Team!
> > It keeps getting better and better!
> > And thank you very much for improving cpyext.
> >
> > > Fix edge cases in the cpyext refcounting-compatible semantics (more
> > work on cpyext compatibility is coming in the cpyext-ext branch, but
> > isn’t ready yet)
> >
> > So thats mean , soon, infuture , cpyext will be fully supported?
> >
> For some definition of 'infuture' and 'fully' - yes.
> The larger goal is to enable the scientific python stack with only minor
> upstream changes, IMO cpyext-ext will be finished when numpy's test
> suite passes with no failures on the fork of numpy available on github
> at github.com/pypy/numpy (not to be confused with the one at
> bitbucket/pypy/numpy, which uses micronumpy and cffi)
>
> Eventually, we will modify micronumpy so that app-level python calls
> with ndarrays will somehow be hijacked to go through micronumpy rather
> than the C-API functions, assuming this is even possible.
>
> It is a big job, help is welcome
> Matti
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20160422/73368076/attachment.html>