Show HN: Varnishtuner.py

Re:Show HN: Varnishtuner.py by e12e on Saturday April 18, 2015 @07:27PM (#9401483)

Admittedly, I generally write procedural and/or functional python code... but how is:

  class CPUInfo(dict):
	def __init__(self, *args):
		dict.__init__(self, args)

	def __getitem__(self, key):
		val = dict.__getitem__(self, key)
		return val

	def __setitem__(self, key, val):
		dict.__setitem__(self, key, val)

Different from:

    class CPUInfo(dict):
        pass

Doesn't the overrides behave just like dict does?

[ Parent | on HN ]

Re:Show HN: Varnishtuner.py by bliti on Sunday April 19, 2015 @12:36AM (#9402043)

Author probably has future plans for the class. I've seen people write classes like that to later do overloading. Others write out the methods to sort of document that those are the ones they are using. I know it might not be one's cup of tea, but let he who writes perfect code every time push to production without testing it first.

[ Parent | on HN ]

Re:Show HN: Varnishtuner.py by e12e on Sunday April 19, 2015 @05:59AM (#9402595)

Well, it's nice to see my intuition was right. Seems a little redundant as documentation - at least for classes in the standard lib. And I'd prefer the diff from "pass" to "added overloaded method" rather than "changed standard method". I think.

[ Parent | on HN ]

Re:Show HN: Varnishtuner.py by aeikenberry on Saturday April 18, 2015 @10:09PM (#9401787)

I was going to ask the same thing.

[ Parent | on HN ]