Sunday, November 1, 2015, 21:24:40 Slide:
|
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? |
The only idea I have is: the primary candidate for fixing a bug is someone who is suffering from it.
Even if they can't fix it themselves (setting up a dev env is nontrivial, and IPy doesn't come with
debug symbols to debug the stock instance), they can, at least, track the cause or be asked to provide a
reproducible example.
--
Regards,
Ivan Pozdeev
_______________________________________________ Ironpython-users mailing list Ironpython-users@python.org https://mail.python.org/mailman/listinfo/ironpython-users
