News for hackers. Stuff that matters.
Re:Molten: A modern Python (3.6+) web framework by Waterluvian on Monday October 01, 2018 @03:14AM (#18110587)
Do you mean remove self from the method signature or altogether?

I think the latter is fundamentally impossible. There would be name collisions and it would be horribly ambiguous. I assume you're suggesting the former.

I can see it being plausible. I'm not sure I have a really clear case against it. I do really like that things are explicit. There's no magical place "self" emerges from. I hate this about some other languages, like JavaScript's 'attributes' collection that magically exists in a function context.

Being able to juggle binded and unbinded functions is nice. The explicit self or cls kind of forces you to declare what the intent of your function is.

Not super clear. But the ship has sailed on that issue. Not sure it could be changed in a non breaking way.

Re:Molten: A modern Python (3.6+) web framework by meowface on Monday October 01, 2018 @03:19AM (#18110603)
Ah sorry, I meant from the method signature. I wouldn't like the totally implicit `self` / `this` found in Java.

>Being able to juggle binded and unbinded functions is nice. The explicit self or cls kind of forces you to declare what the intent of your function is.

Sure, but we can already do that with the @classmethod decorator. They could just make it so `cls` is a variable that can be accessed from any method. If it's a class method, `cls = self`, otherwise, `cls = self.__class__`.