[issue13972] set and frozenset constructors don't accept multiple iterables

2012-02-15 Thread Petri Lehtinen
Petri Lehtinen added the comment: Ok, closing because of lack of support for the idea. -- resolution: -> wont fix status: open -> closed ___ Python tracker ___

[issue13972] set and frozenset constructors don't accept multiple iterables

2012-02-11 Thread Terry J. Reedy
Terry J. Reedy added the comment: I believe s = set(); s.update(s1, s2, s3, ...) a) does what is requested; b) is the proper spelling, as the request *is* for a union of input collections. So I recommend closing. -- nosy: +terry.reedy ___ Python tra

[issue13972] set and frozenset constructors don't accept multiple iterables

2012-02-10 Thread Éric Araujo
Éric Araujo added the comment: As a set user (not developer), I think that the proposed feature is not needed, and the change would make set/frozenset less similar to list and tuple, which would be a bad thing. -- nosy: +eric.araujo ___ Python trac

[issue13972] set and frozenset constructors don't accept multiple iterables

2012-02-10 Thread Raymond Hettinger
Raymond Hettinger added the comment: It is present in union and intersection because chained operations are reasonably common. I don't think it makes much sense in the constructors because it doesn't correspond to how people think of (make this a set). -- assignee: -> rhettinger nos

[issue13972] set and frozenset constructors don't accept multiple iterables

2012-02-09 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue13972] set and frozenset constructors don't accept multiple iterables

2012-02-09 Thread Petri Lehtinen
New submission from Petri Lehtinen : set.update() and friends accept multiple iterables. IMHO, set and frozenset constructors should, too. -- components: Interpreter Core messages: 152931 nosy: petri.lehtinen priority: normal severity: normal status: open title: set and frozenset constr