Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #100471 > unrolled thread

Re: subclassing collections.Counter

Started byPavlos Parissis <pavlos.parissis@gmail.com>
First post2015-12-15 17:20 +0100
Last post2015-12-15 17:20 +0100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: subclassing collections.Counter Pavlos Parissis <pavlos.parissis@gmail.com> - 2015-12-15 17:20 +0100

#100471 — Re: subclassing collections.Counter

FromPavlos Parissis <pavlos.parissis@gmail.com>
Date2015-12-15 17:20 +0100
SubjectRe: subclassing collections.Counter
Message-ID<mailman.31.1450196467.22044.python-list@python.org>

[Multipart message — attachments visible in raw view] — view raw

On 15/12/2015 05:11 μμ, Ian Kelly wrote:
> On Tue, Dec 15, 2015 at 8:49 AM, Pavlos Parissis
> <pavlos.parissis@gmail.com> wrote:
>> Hi,
>>
>> I need to store values for metrics and return the average for some
>> and the sum for the rest. Thus, I thought I could extend
>> collections.Counter class by returning averages for some keys.
> 
> Leave Counter out of it, as this is not what it's designed for. Write
> a custom Metrics class, with each attribute being a pseudo-collection
> that maintains a sum or average.
> 

But then I will have to override a lot of magic methods, right?
What is the real problem of extending Counter in the way I did?

Cheers,
Pavlos

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web