Author rhettinger
Recipients bethard, gvanrossum, pitrou, rhettinger
Date 2009-01-09.21:36:44
SpamBayes Score 0.000107289
Marked as misclassified No
Message-id <1231537005.8.0.813817689101.issue1696199@psf.upfronthosting.co.za>
In-reply-to
Content
The counts/counter moniker emerged from the python-dev discussion and
I'm basically happy with it since the typical usage is c=Counter(myseq)
with no other non-dict accesses (mostly just c[elem]+=1 and print
c[elem]).  It's a simple counter with a dict interface so the name
shouldn't suggest anything more complicated than that.

To me, MultiSet or CountingSet is too offputtingly computer-sciency and
misleadingly suggests a set-like API instead of a dict interface. I know
several programmers who don't know the terms, bag or multiset, but they
intuitively understand what a counter does.  Am open to calling it a Bag
but I rather like the self-descriptiveness and simplicity of Counter.  

As noted previously, standalone unittests are forthcoming (and a doc
patch).  Wanted to get the API and sample use cases worked-out first.

Thanks for looking at the initial patch.
History
Date User Action Args
2009-01-09 21:36:46rhettingersetrecipients: + rhettinger, gvanrossum, pitrou, bethard
2009-01-09 21:36:45rhettingersetmessageid: <1231537005.8.0.813817689101.issue1696199@psf.upfronthosting.co.za>
2009-01-09 21:36:45rhettingerlinkissue1696199 messages
2009-01-09 21:36:44rhettingercreate