3 ms·
The last few years the discussions of new features if Python have been in two categories: 1. Changes that broke backward compatibility introducing mostly unimp
by antman 6y ago
The last few years the discussions of new features if Python have been in two categories:
1. Changes that broke backward compatibility introducing mostly unimportant features
2. Changes that introduced outright mostly unimportant features adding complexity
Instead python programmers' grievances as per "Desired python features" in python surveys [0] are being pushed back.
Top ten programmers' requests actually as per [0] are: static typing, better performance, better concurrency (async syntax...), switch statement (introduced with mindbending gotcha), jit, improve standard library, improve package management, mobile, multiline lambdas, gui.
It appears conclusive discussions in python boards are similar to what Nokia executive board minutes would look like a few years back.
[0]: https://www.jetbrains.com/lp/python-developers-survey-2020/ https://www.jetbrains.com/lp/python-developers-survey-2020/
- fabioz 6y agoWell, this particular change (PEP 563) is IMHO actually striving for improved static typing and better performance, so, I guess they're in sync with that. -- PEP 649 would undo those performance improvements and possibilities of improved static typing over concerns of libraries that user types at runtime having to adapt (I took a look at the issues reported at pydantic and while the API would need to be adapted when PEP 563 would come into effect, I don't really see the major breakage they're talking about -- not that it doesn't take some work to adapt, but I don't see the reason it'd suddenly become impossible to do, it'd only make their own lives a bit easier over the performance cost of all the libraries that use typing without requiring runtime information).