On Mon, Nov 9, 2009 at 7:01 PM, Guido van Rossum <gu...@python.org> wrote: > On Mon, Nov 9, 2009 at 3:44 PM, geremy condra <debat...@gmail.com> wrote: >> the idea >> that we shouldn't put blinking lights and sirens on the crushomatic 9000 >> because people might eventually ignore them doesn't strike me as being >> all that smart. > > I'm sorry, but you're really not getting the point. The crushomatic > already *has* a blinking light and a siren and everyone is *already* > ignoring them, because they go off all the time, whenever a person > gets closer than 6 feet. So we have no way to warn them when there > *really* is a danger, like when a person is about to put their hand > into the blender. > > The solution is to make the machine less dangerous (e.g. if you open > the lid the motor is cut off), not to argue that the siren is really > important.
Rereading my post I don't see any place where I seem to have argued that deprecation warnings were "really important", but in case that's how it sounded, let me clarify: I don't think this argument is anything other than lots and lots of bikeshedding, since these warnings can already be explicitly silenced by the very people this is designed to protect. Having said that, if you think that deprecation warnings are mostly noise, why not ask the pylint and pychecker devs to handle that and drop the warnings altogether? Geremy Condra _______________________________________________ stdlib-sig mailing list stdlib-sig@python.org http://mail.python.org/mailman/listinfo/stdlib-sig
