News for hackers. Stuff that matters.
Re:PEP 3107 – Function Annotations in Python 3 by jerf on Monday May 12, 2014 @08:47AM (#7732373)
Lacks compositional abilities as specified, which is unfortunate. If two libraries want to use this at the same time for two different purposes, there's no standard given for it.

I guess I have to admit that my feeling is that in our rich existing language ecosystem, features that seem designed to help turn Python into something it isn't just waste time and steps Python that much closer to Enterprise-class complexity. Maybe what Python really needs most right now is just a straight-up language freeze. It's done, it is what it is, what it is is pretty darned good for a lot of use cases, and that last bit can't be highlighted enough. It isn't going to be a static language wonder, it isn't going to have generalized C-class performance, it isn't going to become a great hugely-concurrent multithreading language, and you know what? That's OK. It's better to be a good Python than to be a bad not-quite-anything.

Re:PEP 3107 – Function Annotations in Python 3 by pekk on Monday May 12, 2014 @01:16PM (#7734024)
By a language freeze, you mean that Python should never change again?
Re:PEP 3107 – Function Annotations in Python 3 by jerf on Monday May 12, 2014 @02:14PM (#7734436)
Or at least, raise the bar on changes much, much higher. Total freeze is probably an unrealistic goal, but a at least a "conceptual" freeze, yes.