<div dir="ltr"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
> > This information really belongs in <a href="http://www.python.org/dev/" target="_blank">www.python.org/dev/</a> rather than<br>
> > only in the mailing list.<br>
> ><br>
> +1<br>
><br>
> As does a recent essay by Eli Bendersky, IMO. I believe it could lower<br>
> the barriers for entry into the "non-committer" class of developer. This<br>
> should make it easier for people to adapt Python to their own purposes<br>
> whether or not they want to contribute to the open source code base, but<br>
> also encourage people to investigate the compiler's innards.<br>
<br>
</div>With the moratorium on language constructs and builtins (not only in<br>
letter until 3.3, but more generally in spirit), I don't think we should<br>
encourage it at all, for such contributions would surely be rejected.<br>
<br>
Rather than fancy syntax propositions or wild semantic<br>
changes/enhancements (such as have often been proposed on<br>
python-ideas), what we need is humbler but more useful work on stdlib<br>
bugs and improvements, as well as documentation and tutorials.<br>
<br>
(what's more, those two kinds of contributions are likely to attract<br>
two different kinds of people, which means that people whose syntax<br>
patches get refused won't necessarily start contributing stdlib or<br>
documentation patches...)<br>
<br>
Regards<br>
<font color="#888888"><br>
Antoine.<br>
</font><br></blockquote><div><br>Antoine,<br><br>I wrote that article, and I agree with everything you say here. I just don't want my intentions to be understood incorrectly. Many readers stopped reading after the title and jumped to conclusions which simply aren't true (as some of the comments on the blog and Reddit demonstrate). Just a couple of quotes from the article itself to show that breaking the moratorium (with which I wholeheartedly agree) is far from my intentions:<br>
<br>-----------------------------<br>This article is an attempt to better understand how the front-end of
Python works. Just reading documentation and source code may be a bit
boring, so I’m taking a hands-on approach here: I’m going to add an <tt class="docutils literal"><span class="pre">until</span></tt> statement to Python.<br>[...]<br>This article doesn’t attempt to suggest the addition of an <tt class="docutils literal"><span class="pre">until</span></tt>
statement to Python. Although I think such a statement would make some
code clearer, and this article displays how easy it is to add, I
completely respect Python’s philosophy of minimalism. All I’m trying to
do here, really, is gain some insight into the inner workings of Python.<br>-----------------------------<br><br>Kind regards,<br>Eli<br><br><br><br><br> </div></div></div>