Re: [Python-Dev] PEP 3003 - Python Language Moratorium
by Glyph Lefkowitz other posts by this author
Nov 7 2009 12:37AM messages near this date
Re: [Python-Dev] PEP 3003 - Python Language Moratorium
|
Re: [Python-Dev] PEP 3003 - Python Language Moratorium
On Nov 6, 2009, at 4:52 PM, exarkun@[...].com wrote:
> On 09:48 pm, rdmurray@[...].com wrote:
> > On Fri, 6 Nov 2009 at 15:48, Glyph Lefkowitz wrote:
> >
> >> Documentation would be great, but then you have to get people to
> >> read the documentation and that's kind of tricky. Better would be
> >> for every project on PyPI to have a score which listed warnings
> >> emitted with each version of Python. People love optimizing for
> >> stuff like that and comparing it.
> >>
> >> I suspect that even if all warnings were completely silent by
> >> default, developers would suddenly become keenly interested in
> >> fixing them if there were a metric like that publicly posted
> >> somewhere :).
> >
> > +1, but somebody needs to write the code...
>
> How would you collect this information? Would you run the test
> suite for each project? This would reward projects with small or
> absent test suites. ;)
*I* would not collect this information, as I am far enough behind on
other projects ;-) but I if I were to advise someone *else* as to how
to do it, I'd probably add a feature to the 'warnings' module where
users could opt-in (sort of like popcon.debian.org) to report warnings
encountered during normal invocations of any of their Python programs.
I would also advise such a hypothetical data-gathering project to
start with a buildbot doing coverage runs; any warning during the test
suite would be 1 demerit, any warning during an actual end-user run of
the application *not* caught by the test suite would be 1000
demerits :).
And actually it would make more sense if this were part of an overall
quality metric, like http://pycheesecake.org/ proposes (although I
think that cheesecake's current metric is not really that great, the
idea is wonderful).
_______________________________________________
Python-Dev mailing list
Python-Dev@[...].org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-dev-ml%40maillist.acti
vestate.com
Thread:
Guido van Rossum
Arfrever Frehtes Taifersar Arahesis
Antoine Pitrou
exarkun
Glyph Lefkowitz
R. David Murray
exarkun
Glyph Lefkowitz
Stephen J. Turnbull
Brett Cannon
Guido van Rossum
Steven D'Aprano
Steven D'Aprano
Guido van Rossum
Scott Dial
Geremy Condra
Jesse Noller
Geremy Condra
Guido van Rossum
Geremy Condra
Brett Cannon
Guido van Rossum
John Arbash Meinel
Greg Ewing
Terry Reedy
Mrab
Dirkjan Ochtman
Brett Cannon
Jesse Noller
Guido van Rossum
Georg Brandl
Nick Coghlan
Guido van Rossum
skip
exarkun
Georg Brandl
Guido van Rossum
Brett Cannon
Guido van Rossum
Brett Cannon
Guido van Rossum
Brett Cannon
Terry Reedy
Geremy Condra
Andre Stechert
Yuvgoog Greenle
Nick Coghlan
Dirkjan Ochtman
Tres Seaver
Nick Coghlan
Bobby R. Ward
exarkun
hfuerstenau
Yuvgoog Greenle
Gregory P. Smith
Georg Brandl
A.M. Kuchling
Georg Brandl
Jesse Noller
Raymond Hettinger
Stefan Behnel
Stefan Behnel
Michael Foord
Stefan Behnel
Michael Foord
Stefan Behnel
Maciej Fijalkowski
Stefan Behnel
Dirkjan Ochtman
Thomas Heller
Guido van Rossum
Stefan Behnel
Antoine Pitrou
Stefan Behnel
Guido van Rossum
Anand Balachandran Pillai
Willem Broekema
Maciej Fijalkowski
Stefan Behnel
Michael Foord
Steven D'Aprano
Willem Broekema
Steven D'Aprano
Willem Broekema
Stefan Behnel
Dino Viehland
Stefan Behnel
Dino Viehland
Collin Winter
Alexandre Vassalotti
Jack Diederich
Nick Coghlan
Mark Hammond
Facundo Batista
Jesse Noller
Barry Warsaw
Michael Foord
Doug Hellmann
skip
M.-A. Lemburg
Guido van Rossum
Stephen J. Turnbull
Brett Cannon
Guido van Rossum
martin
Guido van Rossum
Antoine Pitrou
|