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 ethan.furman
Recipients cool-RR, eric.smith, ethan.furman, josh.r, pitrou, r.david.murray, rhettinger, serhiy.storchaka, steven.daprano
Date 2014-10-01.16:57:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412182678.22.0.190247062498.issue22515@psf.upfronthosting.co.za>
In-reply-to
Content
--> s1 = set([1])
--> s2 = set([1, 2])
--> s3 = set([1, 2, 3])
--> s4 = set([2])
--> s5 = set([2, 3])
--> s6 = set([3])

--> l = [s1, s2, s3, s4, s5, s6]
--> sorted(l)
[{1}, {2}, {1, 2}, {3}, {2, 3}, {1, 2, 3}]

--> s1 < s4
False

--> s4 < s2
True

--> s1 < s2
True

--> s4 < s6
False

--> l = [s1, s4]
--> sorted(l)
[{1}, {2}]

--> sorted(l)
[{1}, {2}]


Looks horribly messy to me.  In the last example we can see that neither s1 nor s4 are smaller, yet s1 is consistently put first.

On the other hand, I suppose it's okay for Counter to have this behavior since it's already in sets.
History
Date User Action Args
2014-10-01 16:57:58ethan.furmansetrecipients: + ethan.furman, rhettinger, pitrou, eric.smith, steven.daprano, r.david.murray, cool-RR, serhiy.storchaka, josh.r
2014-10-01 16:57:58ethan.furmansetmessageid: <1412182678.22.0.190247062498.issue22515@psf.upfronthosting.co.za>
2014-10-01 16:57:58ethan.furmanlinkissue22515 messages
2014-10-01 16:57:57ethan.furmancreate