Hi Phyo. I am not sure, since I'm so deep in, it's hard to say what level of expertise is required. I would imagine one would have to know how to write snippets of code in the C-API of python, and certainly would have to be familiar with the PyPY development process. A familiarity with a beloved (to them) C-API based module would probably also help, so they can say when it is working properly. Maybe some others have an opinion? Matti On 22/04/16 15:17, Phyo Arkar wrote:

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@gmail.com <mailto:matti.picus@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 <http://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@python.org <mailto:pypy-dev@python.org> https://mail.python.org/mailman/listinfo/pypy-dev