On 2010-02-19 16:23, Nick Coghlan wrote: > Sjoerd Mullender wrote: >> My point is, as a matter of *policy*, nothing should be released that >> uses deprecated stuff. I can't create a bug report about wrong (or >> incomplete) policies. > > The policy is more that the test suite shouldn't raise Deprecation > Warnings unless it is explicitly checking for them (or otherwise testing > known-deprecated code). The policy should also be, if someone decides (or rather, implements) a deprecation of a module, they should do a grep to see where that module is used and fix the code. It's not rocket science. > If there is a hole in the test suite coverage such that paths that > trigger deprecated code are not exercised by the regression tests, then > that is a bug. > > Cheers, > Nick. > -- Sjoerd Mullender -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 371 bytes Desc: OpenPGP digital signature URL: <http://mail.python.org/pipermail/python-dev/attachments/20100219/63451b43/attachment.pgp>
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