News for hackers. Stuff that matters.
Re:PyPy2.7 and PyPy3.5 v5.7 released by kzrdude on Tuesday March 21, 2017 @01:30PM (#13924341)
But it sounds like he implicitly hinders CPython! It sounds like “we won't merge code I don't understand” and no brave intelligent soul will risk improving the interpreter.
Re:PyPy2.7 and PyPy3.5 v5.7 released by nameless912 on Tuesday March 21, 2017 @11:56PM (#13928349)
Isn't that the explicit job of a BDFL though? To enforce standards? His happens to be simplicity at all costs, and while some might disagree, I think it's generally a good pursuit; as others state, alternative implementations are available if you really need some JITing black magic or Java integration or green threads or...
Re:PyPy2.7 and PyPy3.5 v5.7 released by milesrout on Wednesday March 22, 2017 @02:13AM (#13928818)
What's wrong with "we won't merge code we don't understand"? I think a lot of people should hold code to that standard. I think almost everyone does hold code to that standard.
Re:PyPy2.7 and PyPy3.5 v5.7 released by kzrdude on Wednesday March 22, 2017 @05:27AM (#13929539)
It's a problem when leadership is not ~~merit~~ engagement based (BFDL) and when said leadership is lacking the vision and gut to push Python across new boundaries. I would like to see something more “aggressive” here.
Re:PyPy2.7 and PyPy3.5 v5.7 released by milesrout on Wednesday March 22, 2017 @06:38PM (#13935689)
The leadership of Python, in the form of Guido, is certainly merit- and engagement-based. Nothing needs to be 'more aggressive' in Python development. It's perfectly fine for the standard, canonical version of Python to be the version that:

* Is most up-to-date and has all the latest features * Everyone is most familiar with * Already is packaged in all operating systems * Is the most stable * Is compatible with all C extensions