Hacker News Reader

This is a pretty good overview of some key deficiencies. I wish he would have left the "not backwards compatible" complaints out -- backwards compatibility is a well-known non-goal, and it's a non-issue how difficult (or subtle) porting code to Py3 from Py2 is.

The super() stuff is unfortunate. It seems that Py3 manages to clean up so very many other uglinesses of the language... to see a new, obviously ugly thing introduced...

View on HN

Could you (or anyone else) elaborate on the issues with super() as described in this article? I'm having a hard time understanding what's going on between the complex details of the problem and the author's cumbersome syntactic choices.

I'm not sure if this is really clear, but it's better: http://docs.python.org/library/functions.html#super

The super() is magical. Functions aren't supposed to magically know what class or instance they are in unless they are explicitly passed on in Python. That's why you see the "self" argument in methods.

And in the 2nd example, he shows that if you copy super to another name, then it doesn't work. Presumably meaning that super which looks like a function, actually acts like a compiler keyword in certain cases.

Reply on news.ycombinator.com