[Python-ideas] Proposal: Moratorium on Python language changes
g.brandl at gmx.net
Sun Oct 25 17:42:51 CET 2009
Guido van Rossum schrieb:
> On Sun, Oct 25, 2009 at 12:01 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> Moving to a DVCS, putting a core language change moratorium in place for
>> a few years, then looking to see what improvements have been developed
>> outside the core tree as the moratorium is running down (and what
>> feedback has been received over that time) would be far more sensible.
> But the merges into the core will be tough. Imagine submitting a
> 5000-line patch and saying "I've worked on this for a year, please
> adopt it." Will we do enough code review to assert the code quality?
I can see two remedies:
* The branch changes are structured in relatively short, well-reviewable
commits. Less likely for a branch worked on for a year though.
* A core developer is involved from the start and acts as a just-in-time
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.
More information about the Python-ideas