<br><br><div class="gmail_quote">On Mon, Mar 2, 2009 at 4:22 PM, "Martin v. Löwis" <span dir="ltr"><<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> Would whoever is responsible for IDLE please take a look at the patches<br>
> I submitted for Python 2 & 3 [tracker IDs 5233 and 5234 respectively].<br>
> These change the behavior of IDLE so that IDLESTARTUP or PYTHONSTARTUP<br>
> files are executed with each restart. This allows loading frequently<br>
> used packages, personal utilities, etc. automatically at each restart. I<br>
> consider this a very important problem in IDLE, especially when using it<br>
> to teach.<br>
<br>
</div>Just to put this into perspective: I personally don't see that as a very<br>
important problem. I didn't know IDLESTARTUP existed, and I use<br>
PYTHONSTARTUP only for the command line (to setup readline and history).<br>
I think there are many more open issues that are *way* more important.</blockquote><div><br></div><div>Martin,</div><div><br></div><div> No disrespect intended but I don't see how this puts things into perspective. I'm writing to you from the annual computer science education conference (SIGCSE) where Python is clearly gaining ground as an important language for teaching computer science.</div>
<div><br></div><div>It seems logical to me that the committers are high powered Python users who don't think much about Python being used in education. I'm just as frustrated as Mitchell about a patch for displaying ranges and dict_keys/values objects in a more user friendly way. I submitted this patch during the 3.0 alpha phase and it is still sitting around. For me this is a serious problem, but I can understand how it seems pretty minor to others, who are not teaching new programmers.</div>
<div><br></div><div>So what is the solution? The obvious solution is for one of us, that is someone who uses Python as an education tool, to become a committer. This seems problematic to me. Although I'm willing to be a committer, and I'm confident I have the development skills necessary to be a committer I don't have the time to develop the resume of patches needed to earn that privilege.</div>
<div><br></div><div>It would be nice if we could find some solution to this.</div><div><br></div><div>Brad</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
This is not to say that the patch should not applied - I haven't even<br>
looked at it. It's just a warning that, if no other committer feels this<br>
is as important as you fell it is, it may not be committed reviewed and<br>
committed before 3.1.<br>
<br>
Regards,<br>
<font color="#888888">Martin<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-dev" target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/bmiller%40luther.edu" target="_blank">http://mail.python.org/mailman/options/python-dev/bmiller%40luther.edu</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Brad Miller<br>Assistant Professor, Computer Science<br>Luther College<br>