[Python-Dev] pending deprecation warning for Set.update (original) (raw)
Raymond Hettinger python at rcn.com
Wed Sep 17 12🔞15 EDT 2003
- Previous message: [Python-Dev] pending deprecation warning for Set.update
- Next message: [Python-Dev] pending deprecation warning for Set.update
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeremy> It looks like current CVS has grown a pending deprecation Jeremy> warning for the update() method of Sets ... [Skip] +1 on everything Jeremy wrote.
One other thought: having a PendingDeprecationWarning is somewhat
innocuous. By default, those warnings are filtered out (set to Ignore).
You have to ask to see them. It would be much different for a
DeprecationWarning.
It is pretty conservative to issue a pending warning now, a deprecation warning in 2.4, and remove the duplicate method in 2.5. This is doubly true for a brand new module that has only a minimal existing code base. Not bringing it up for 12 to18 months is, IMHO, much more impactful.
Raymond
- Previous message: [Python-Dev] pending deprecation warning for Set.update
- Next message: [Python-Dev] pending deprecation warning for Set.update
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]