[Ironpython-users] Attracting new developers
Tim Orling
ticotimo at gmail.com
Wed Nov 4 16:21:51 EST 2015
I have no suggestions, but completely agree with the sentiment. In
particular, I would love to see some traction on PEP-380
<https://github.com/IronLanguages/ironpython3/issues/1>, since that is the
first thing that came up when I tried to use IP3.
I had a look at the code
<https://github.com/IronLanguages/ironpython3/blob/master/Src/IronPython/Compiler/Ast/YieldExpression.cs>,
but it's not obvious how to proceed, even after looking at the cpython code
<https://github.com/python/cpython/blob/1fe0fd9feb6a4472a9a1b186502eb9c0b2366326/Python/Python-ast.c#L1982>.
(Hence why jdhardy labels that issue "hard
<http://blog.jdhardy.ca/2013/06/ironpython-3-todo.html>").
I at least am willing to step in and help.
On Sun, Nov 1, 2015 at 10:24 AM, Slide <slide.o.mix at gmail.com> wrote:
> It seems like there has been a general lack of development on IronPython
> for the past little while. I know I have been super busy and I'm sure other
> developers have as well. Does anyone have any ideas on attracting new
> developers to start working on 1) fixing issues in the 2.7 line 2) get
> IP3.0 out the door?
>
> _______________________________________________
> Ironpython-users mailing list
> Ironpython-users at python.org
> https://mail.python.org/mailman/listinfo/ironpython-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20151104/37275691/attachment.html>
More information about the Ironpython-users
mailing list