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

2005-07-01 Thread Barry Warsaw
On Thu, 2005-06-30 at 13:37, Raymond Hettinger 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(). > > No. It was intentional to drop the duplicate method with the > hard-to-u

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

2005-06-30 Thread Raymond Hettinger
> 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(). No. It was intentional to drop the duplicate method with the hard-to-use name. There was some thought given to deprecating sets.union_upda

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

2005-06-30 Thread Aahz
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 texinf