On Fri, 6 Nov 2009 at 15:48, Glyph Lefkowitz wrote: > On Nov 6, 2009, at 9:04 AM, exarkun at twistedmatrix.com wrote: >> End users don't even need to be told this much, though (and if it's javac >> that does this for Java, then indeed Java end users probably aren't seeing >> this either). I think it would be great for deprecation warnings to be >> completely silent for a while *and* for the policy to be prominently >> documented so that developers, the people who really need this information, >> know how to get it. > > 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... --David (RDM)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4