On Mon, Nov 9, 2009 at 6:09 PM, Raymond Hettinger <pyt...@rcn.com> wrote: > > [Brett Cannon] >> >> This is obviously coming down to difference of opinion. I don't view >> switching warnings off by default as shooting anyone in the foot. I >> put it on the same level as making sure you have unit tests; it's just >> part of your testing and verification process that your users just >> don't need to know about. > > Nice summary. FWIW, I concur with Brett. No one needs to see > warnings/deprecations except for the developer who controls the code. > Even that developer may only need to see it at one point during the > development process. Further, the developer controlling the code > just may not care -- the script can be for single use, for a class project, > or some other purpose that doesn't require being notified of what may > change in a later version of Python. > > > Raymond
If they don't care, why does it matter whether they see it or not? Seems like an argument for the status quo. Geremy Condra _______________________________________________ stdlib-sig mailing list stdlib-sig@python.org http://mail.python.org/mailman/listinfo/stdlib-sig
