3 ms·
> no alternative > have to What? People are just making decisions about how they want the language to evolve, how they want to coordinate production-grade rele
by swatcoder 3y ago
> no alternative
> have to
What? People are just making decisions about how they want the language to evolve, how they want to coordinate production-grade releases, and how they approach backwards compatibility in those contexts.
Nothing about those decisions is necessitated or even strongly pressured. They're just an artifact of the Python community's particular engineering culture, and it's one that's uncommonly hostile to streamlined distribution or to shelving application code as stable and "done".
- whatever1 3y agoI don't understand your claim that this is a python specific issue. There are C++ libraries that require C++11. As a result if you have an older compiler that does not support C++11 it will just not compile. Same if you try to compile with C++11 compiler a super old project with old libraries. More likely than not it will break. The fact that other languages ignore the problem, it does not make the problem go away. At least python is pragmatist and comes with virtual environments instead of requiring me to set up containers or VMs to deal with package compatibility.