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 terry.reedy
Recipients BTaskaya, Pixmew, docs@python, rhettinger, terry.reedy
Date 2020-11-14.07:13:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1605338033.52.0.179862191566.issue42348@roundup.psfhosted.org>
In-reply-to
Content
Raymond's last point is that set objects should be immutably hashable.  I would say 'must be' in the sense that mutably hashable objects break sets in various ways, starting with uniqueness.  If we were to make a change, I think the replacement should be 'immutably hashable'

'unique objects' would also need qualification.  As is, one might reasonably expect. for instance, {1+0j, 1.0, 1} to have 3 elements rather than 1.  It is really 'objects unique up to equality', where equality may or may not be by identity.

However, I am inclined to agree with Raymond that we should stick to the current easily read sentence.
History
Date User Action Args
2020-11-14 07:13:53terry.reedysetrecipients: + terry.reedy, rhettinger, docs@python, BTaskaya, Pixmew
2020-11-14 07:13:53terry.reedysetmessageid: <1605338033.52.0.179862191566.issue42348@roundup.psfhosted.org>
2020-11-14 07:13:53terry.reedylinkissue42348 messages
2020-11-14 07:13:53terry.reedycreate