Juan Benavente Ponce added the comment:
set.intersection and frozenset.intersection docstrings are back to the wrong
two-sets-only version in Python 3.3 (Python 2.7 is not affected):
intersection(...)
Return the intersection of two sets as a new set.
(i.e. all elements that are
Juan Benavente Ponce added the comment:
Comparing the docstrings with the on-line documentation, I have found that, in
addition to the already mentioned issue, the fact that many methods only
require the first argument to be a set (or frozenset) object is not mentioned
anywhere in the
Changes by Raymond Hettinger rhettin...@users.sourceforge.net:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7263
___
New submission from Alexander Belopolsky belopol...@users.sourceforge.net:
intersection(...)
Return the intersection of two sets as a new set.
(i.e. all elements that are in both sets.)
Is incorrect because set.intersection takes two or more sets.
Attached patch changes that to
Changes by Raymond Hettinger rhettin...@users.sourceforge.net:
--
assignee: georg.brandl - rhettinger
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7263
___
