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 belov
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 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 impro
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)
Last night we released PyPy 5.1, thanks to all involved.
Matti
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
