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 stutzbach
Recipients hyeshik.chang, loewis, rhettinger, stutzbach
Date 2009-03-30.20:25:13
SpamBayes Score 9.440697e-09
Marked as misclassified No
Message-id <1238444715.49.0.180609134425.issue1324770@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with Raymond.

In general, the collections module should define containers that are
named after their function rather than their implementation.  That way
the implementation can be changed at a later date (or in other Python
implementations) without causing confusion, and it makes it more obvious
what use-case the new collection is solving.  That's my opinion, anyway.

As much as I'd love to see more container types in the collections
module (my kingdom for a heap with .decrease_key()!), I don't see what
use-case this implementation of red-black trees fills.
History
Date User Action Args
2009-03-30 20:25:15stutzbachsetrecipients: + stutzbach, loewis, rhettinger, hyeshik.chang
2009-03-30 20:25:15stutzbachsetmessageid: <1238444715.49.0.180609134425.issue1324770@psf.upfronthosting.co.za>
2009-03-30 20:25:14stutzbachlinkissue1324770 messages
2009-03-30 20:25:13stutzbachcreate