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 josh.r
Recipients DeadmanWalking, docs@python, josh.r, rhettinger, xtreak
Date 2019-03-06.03:57:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551844620.31.0.882758636016.issue36198@roundup.psfhosted.org>
In-reply-to
Content
The "returns" bit is accurate when referring to the in-place operator overloads (__ior__), so those lines may have been written referring to the overloads described on the same line (they shouldn't have been written that way, but that would explain why only the methods with in-place overload equivalents use the word "returns").

Either way, sets was deprecated in 2.6, largely pointless in every version but 2.3 (module added in 2.3, built-in set/frozenset types added 2.4), and gone in 3.0+ (and 2.7 is EOL within the year). Do we even do doc updates for stuff this dead?
History
Date User Action Args
2019-03-06 03:57:00josh.rsetrecipients: + josh.r, rhettinger, docs@python, xtreak, DeadmanWalking
2019-03-06 03:57:00josh.rsetmessageid: <1551844620.31.0.882758636016.issue36198@roundup.psfhosted.org>
2019-03-06 03:57:00josh.rlinkissue36198 messages
2019-03-06 03:57:00josh.rcreate