> On Dec 27, 2019, at 19:48, Tim Peters wrote:
>
> So, ya, I've seen and implemented lots of work queues along these
> lines - but an OrderedSet would be an "attractive nuisance"
> (offhandedly appearing to solve a problem it doesn't actually
> address):
>
> jobs = some_kind_of_queue()
> finis
[Nick Coghlan ]
> I took Larry's request a slightly different way: he has a use case where
> he wants order preservation (so built in sets aren't good), but combined
> with low cost duplicate identification and elimination and removal of
> arbitrary elements (so lists and collections.deque aren't g
ACTIVITY SUMMARY (2019-12-20 - 2019-12-27)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open7203 ( +3)
closed 43688 (+26)
total 50891 (+29)
Open issues w
On Tue, 24 Dec 2019 12:08:33 +0900
"Stephen J. Turnbull" wrote:
> David Mertz writes:
>
> > Even though I was the first person in this thread to suggest
> > collections.OrderedSet, I'm "meh" about it now. As I read more and played
> > with the sortedcollections package, it seemed to me that wh
