Jeffrey Yasskin wrote:
On Sat, Apr 4, 2009 at 11:52 AM, Collin Winter <coll...@gmail.com> wrote:
On Sat, Apr 4, 2009 at 7:33 AM, Michael Foord <fuzzy...@voidspace.org.uk> wrote:
Antoine Pitrou wrote:
Nick Coghlan <ncoghlan <at> gmail.com> writes:
C. Titus Brown wrote:
I vote for a separate mailing list -- 'python-tests'? -- but I don't
know exactly how splintered to make the conversation. It probably
belongs at python.org but if you want me to host it, I can.
If too many things get moved off to SIGs there won't be anything left
for python-dev to talk about ;)
There is already an stdlib-sig, which has been almost unused.
stdlib-sig isn't *quite* right (the testing and benchmarking are as much
about core python as the stdlib) - although we could view the benchmarks and
tests themselves as part of the standard library...
Either way we should get it underway. Collin and Jeffrey - happy to use
stdlib-sig?
Works for me.
Me too.
bcc python-dev, -> stdlib-sig
First question: Do people want the unladen-swallow performance tests
in the CPython repository until the whole library gets moved out? If
so, where? Tools/performance? Lib/test/benchmarks?
I'm +1 on including them (so long as they run under trunk of course) but
agnostic on location.
Maybe better not in test as it might be expected that a full regrtest
would then run them?
I'm keeping Python-dev cc'd as it is a Python-dev decision and bcc
messages require individual admin approval.
Michael
Jeffrey
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
_______________________________________________
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
