Re: [Python-Dev] Inconsistent API for sets.Set and build-in set

On Thu, Jun 30, 2005, Barry Warsaw wrote:

If there are no objections, I propose to do the following (only in Python 2.4 and 2.5):

  * Add set.union_update() as an alias for set.update().
  * Add to docstrings for all methods that 't' can be any iterable.
  * Update texinfo documentation to add Set.update() and
    set.union_update() and explain that all can take iterables

I consider this a bug in 2.4, not a new feature, because without it, it makes more work in porting applications.

+0 (I'm only not +1 because I don't use sets much -- I'm still mired in Python 2.2 -- but I'm always happy to see inconsistencies resolved)

I'll guess that Raymond will probably want 2.5 to have set.union_update() get a PendingDeprecationWarning.