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 steven.daprano
Recipients DavidMertz, josh.r, mark.dickinson, pitrou, rhettinger, steven.daprano, veky, wolma
Date 2017-03-15.17:25:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489598738.56.0.0947296751662.issue25478@psf.upfronthosting.co.za>
In-reply-to
Content
It seems to me that the basic Counter class should be left as-is, and if there are specialized methods used for statistics (such as normalize) it should go into a subclass in the statistics module.

The statistics module already uses Counter internally to calculate the mode.

It makes some sense to me for statistics to have a FrequencyTable (and CumulativeFrequencyTable?) class built on top of Counter. I don't think it makes sense to overload the collections.Counter type with these sorts of specialised methods.
History
Date User Action Args
2017-03-15 17:25:38steven.dapranosetrecipients: + steven.daprano, rhettinger, mark.dickinson, pitrou, wolma, josh.r, veky, DavidMertz
2017-03-15 17:25:38steven.dapranosetmessageid: <1489598738.56.0.0947296751662.issue25478@psf.upfronthosting.co.za>
2017-03-15 17:25:38steven.dapranolinkissue25478 messages
2017-03-15 17:25:38steven.dapranocreate