This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author hhm
Recipients docs@python, hhm
Date 2013-05-22.11:58:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369223923.83.0.620034016791.issue18032@psf.upfronthosting.co.za>
In-reply-to
Content
It says here (http://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset) that some of the set methods take iterables as a parameter.

Usually, the expected behavior is for a iterator consumer to consume only as much data as it needs. For example, for the code `any(itertools.repeat(True))`, the code will complete speedily, in contrast to when all() is used instead of any(), in which case the code will go forever.

A least some of the set methods have semantics such that they can consume only some of the input; for example, "issubset" only needs to make sure that all of the items in the set are in the iterable, and once this is the case, it can return "True".

However in such a case, the methods will *still* go forever.

The docs should specify that this is the case, to disambiguate the semantics.

(Tested on Python 3.2.3 and 2.7.3).
History
Date User Action Args
2013-05-22 11:58:43hhmsetrecipients: + hhm, docs@python
2013-05-22 11:58:43hhmsetmessageid: <1369223923.83.0.620034016791.issue18032@psf.upfronthosting.co.za>
2013-05-22 11:58:43hhmlinkissue18032 messages
2013-05-22 11:58:43hhmcreate