[Python-Dev] deprecated stuff in standard library

Guido van Rossum guido at python.org
Sat Feb 20 05:46:04 CET 2010


On Fri, Feb 19, 2010 at 5:41 PM, Mike Klaas <mike.klaas at gmail.com> wrote:
> On Fri, Feb 19, 2010 at 9:03 AM, Sjoerd Mullender <sjoerd at acm.org> wrote:
>
>> 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.
>
> I'm not sure if you're aware of it, but you're starting to sound a little rude.

He's just being Dutch. :-)

> ISTM that it doesn't make sense to waste effort ensuring that
> deprecated code is updated to not call other deprecated modules.  Of
> course, all released non-deprecated code should steer clear of
> deprecated apis.

Read again. Sjoerd meant it exactly the other way around. When a
module is deprecated it is *not* a wasted effort to ensure that no
other (undeprecated) modules depend on it!

-- 
--Guido van Rossum (python.org/~guido)


More information about the Python-Dev mailing list