Well, I think Numpy is of huge importance to a major Python user segment, the scientific community. I don't know if that makes it 'core', but I strongly agree that it's important.<div><br></div><div>Better testing is always useful, and more "core", but IMO less important.</div>
<div><br></div><div>-T<br><br><div class="gmail_quote">On Sat, Apr 11, 2009 at 6:38 AM, C. Titus Brown <span dir="ltr"><<a href="mailto:ctb@msu.edu">ctb@msu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all,<br>
<br>
this year we have 10-12 GSoC applications that I've put in the "relevant<br>
to core Python development" category. These projects, if mentors etc<br>
are found, are *guaranteed* a slot under the PSF GSoC umbrella. As<br>
backup GSoC admin and general busybody, I've taken on the work of<br>
coordinating these as a special subgroup within the PSF GSoC, and I<br>
thought it would be good to mention them to python-dev.<br>
<br>
Note that all of them have been run by a few different committers,<br>
including Martin, Tarek, Benjamin, and Brett, and they've been obliging<br>
enough to triage a few of them. Thanks, guys!<br>
<br>
Here's what's left after that triage. Note that except for the four at<br>
the top, these have all received positive support from *someone* who is<br>
a committer and I don't think we need to discuss them here -- patches<br>
etc. can go through normal "python-dev" channels during the course of the<br>
summer.<br>
<br>
I am looking for feedback on the first four, though. Can these<br>
reasonably be considered "core" priorites for Python? Remember, this<br>
"costs" us something in the sense of preferring these over Python<br>
subprojects like (random example) Cython, NumPy, PySoy, Tahoe, Gajim,<br>
etc.<br>
<br>
---<br>
<br>
Questionable "core":<br>
<br>
2x "port NumPy to py3k" -- NumPy is a major Python module and porting it<br>
to py3k fits with Guido's request that "more stuff get ported".<br>
To be clear, I don't think anyone expects all of NumPy to get<br>
ported this summer, but these students will work through issues<br>
associated with porting big chunks o' code to py3k.<br>
<br>
One medium/strong proposal, one medium/weak proposal.<br>
<br>
Comments/thoughts?<br>
<br>
2x "improve testing tools for py3k" -- variously focus on improving test<br>
coverage and testing wrappers.<br>
<br>
One proposes to provide a nice wrapper to make nose and py.test<br>
capable of running the regrtests, which (with no change to<br>
regrtest) would let people run tests in parallel, distribute or<br>
run tests across multiple machines (including Snakebite), tag<br>
and run subsets of tests with personal and/or public tags, and<br>
otherwise take advantage of many of the nice features of nose<br>
and py.test.<br>
<br>
The other proposes to measure & increase the code coverage of<br>
the py3k tests in both Python and C, integrate across multiple<br>
machines, and otherwise provide a nice set of integrated reports<br>
that anyone can generate on their own machines. This proposal,<br>
in particular, could move smoothly towards the effort to produce<br>
a "Python-wide" test suite for CPython/IronPython/PyPy/Jython.<br>
(This wasn't integrated into the proposal because I only found<br>
out about it after the proposals were due.)<br>
<br>
I personally think that both testing proposals are good, and<br>
they grew out of conversations I had with Brett, who thinks that<br>
the general ideas are good. So, err, I'm looking for pushback,<br>
I guess ;). I can expand on these ideas a bit if people are<br>
interested.<br>
<br>
Both proposals are medium at least, and I've personally been<br>
positively impressed with the student interaction.<br>
<br>
Comments/thoughts?<br>
<br>
---<br>
<br>
Unquestionably "core" by my criteria above:<br>
<br>
3to2 tool -- 'nuff said.<br>
<br>
subprocess improvement -- integrating, testing, and proposing some of<br>
the various subprocess improvements that have passed across this<br>
list & the bug tracker<br>
<br>
IDLE/Tkinter patch integration & improvement -- deal with ~120 tracker<br>
issues relating to IDLE and Tkinter.<br>
<br>
roundup VCS integration / build tools to support core development --<br>
a single student proposed both of these and has received some<br>
support. See <a href="http://slexy.org/view/s2pFgWxufI" target="_blank">http://slexy.org/view/s2pFgWxufI</a> for details.<br>
<br>
sphinx framework improvement -- support for per-paragraph comments and<br>
user/developer interface for submitting/committing fixes<br>
<br>
2x "keyring package" -- see<br>
<a href="http://tarekziade.wordpress.com/2009/03/27/pycon-hallway-session-1-a-keyring-library-for-python/" target="_blank">http://tarekziade.wordpress.com/2009/03/27/pycon-hallway-session-1-a-keyring-library-for-python/</a>.<br>
The poorer one of these will probably be axed unless Tarek gives it<br>
strong support.<br>
<br>
--<br>
<br>
--titus<br>
<font color="#888888">--<br>
C. Titus Brown, <a href="mailto:ctb@msu.edu">ctb@msu.edu</a><br>
_______________________________________________<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/tleeuwenburg%40gmail.com" target="_blank">http://mail.python.org/mailman/options/python-dev/tleeuwenburg%40gmail.com</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>--------------------------------------------------<br>Tennessee Leeuwenburg<br><a href="http://myownhat.blogspot.com/">http://myownhat.blogspot.com/</a><br>"Don't believe everything you think"<br>
</div>