Eric S. Johansson wrote: > Diez B. Roggisch wrote: > > Or better even > > > > super(subclass, self).__setitem__(key.upper(), value) > > hmm. http://fuhm.net/super-harmful/
Interesting link, didn't know about it. I've always found super() ugly and doubted that it was in practice better suited for multiple inheritance than explicit method call, but I kept using it nonetheless since it was "blessed" for new style classes. Unless of course the code broke for one of the reasons mentioned in the article, in which case I reverted back to the "old way". Good to know that I can safely get rid of practically all super() calls. Any python-dev-er's take on super()'s utility and future in Py3K ? George -- http://mail.python.org/mailman/listinfo/python-list
