News for hackers. Stuff that matters.
Re:Inside cpyext: Why emulating CPython C API is so Hard by klibertp on Friday September 21, 2018 @04:18PM (#18042372)
> for a total 2-3 person-months of work.

In a year. In a project which could put Python next to JS, for the last pain-point that prevents it.

Python - one of the top 10 most popular languages - community and all its industrial user, including some of the most successful companies on the planet, can afford to put 3 person-months of work for that feature.

There has to be something else at play here that I'm missing. Well, other than missing that "donate" button for a tad too long...

Re:Inside cpyext: Why emulating CPython C API is so Hard by rtpg on Friday September 21, 2018 @07:27PM (#18043419)
There are very few commercial sponsors for Python and related projects. Django has enough resources for basically one full-time paid contributor, but that’s it. Huge amounts of Python infra is maintained in people’s free time, despite powering so much
Re:Inside cpyext: Why emulating CPython C API is so Hard by ma2rten on Saturday September 22, 2018 @12:13AM (#18044413)
Most of the work was done during two sprints, for a total 2-3 person-months of work.

I think what they are saying is just: We got a lot of work done on this during those two sprints. It's not a statement about the work that is remaining.