Mark Dickinson <dicki...@gmail.com> added the comment:
To clarify, are you referring to this behaviour?
>>> a = {1, 2, 3}
>>> b = {1.0, 4.0}
>>> a.intersection(b) # expect {1}
{1.0}
I'd personally expect this to be implementation-dependent: since for set
operations you usually only care about objects up to equality, it would be a
bit unusual to care whether you get {1} or {1.0} in the above situation, and
I'd say the implementation should be free to do whatever's convenient. Making
documented guarantees would unnecessarily constrain other implementations.
I suppose one could document the *lack* of a guarantee here ...
----------
nosy: +mark.dickinson, rhettinger
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32349>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
