On Tue, 19 Apr 2011 14:29:24 +0200, Maciej Fijalkowski <fij...@gmail.com> wrote: > > Once this move is made/accepted, I would expect the other > > implementation to rapidly move away from their custom implementations > > of the stdlib and contribute to the shared code base and > > documentation. Yes, this places a burden on CPython, but in the long > > term in benefits *all* of the projects equally by simply having more > > active contributors. > > I would also like to point out that some valuable contributions were > made already by other implementations. When talking about stdlib, it's > mostly in the area of test suite, but not only in terms of "skip those > tests", but also improving test coverage and even fixing bugs. Unicode > fixes were prototyped on PyPy first and some PyPy optimizations were > ported to CPython (the original method cache patch came from Armin > Rigo as far as I remember). So it's not completely "Cpython's burden" > only.
Yes, and you also need to keep in mind that several developers wear multiple hats, and contribute to CPython on a regular or semi-regular basis. It is also enlightening to look at the output of hg churn. The number of active CPython developers over the past year is not huge, and very few of them have spoken up in this thread. -- R. David Murray http://www.bitdance.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
