>Oh please. The EOL on python2 has been massively pre announced.
Which is neither here, nor there. Pre-announcing doesn't give any reason or motive (or funding) for porting large codebases. Many businesses stuck with 2.x will fund 2.x maintenance if the core devs don't do it, and port on their own schedule not on whatever was "pre announced".
> Oh please. The EOL on python2 has been massively pre announced.
Nope, not when new versions of software comes out with Python 2 still, (can't do anything about those licences bought) small studios cannot afford moving/rewriting tools in P2 to 3, not a priority, rather keep P2.
Then complain to the companies you license software from for continuing to build on a soft-deprecated platform. Don't complain to developers for ignoring a platform whose deprecation was announced over a decade ago.
And certainly don't badmouth people who are using the not-deprecated tool as being ok with unstable infra.
> Then complain to the companies you license software from for continuing to build on a soft-deprecated platform.
You think we haven't been doing this? We had a representative from one of these vendors come in to discuss their roadmap, they told us straight up that "We still intend to keep using Python 2".
> Don't complain to developers for ignoring a platform whose deprecation was announced over a decade ago.
Yes, because web dev is the hot tech stuff now, nobody wants to work in a boring sector, so they are not willing to change anything, cycle continues.
> And certainly don't badmouth people who are using the not-deprecated tool as being ok with unstable infra.
I read this sentence twice and I still don't understand what you're trying to say, clarify?
> Yes, because web dev is the hot tech stuff now, nobody wants to work in a boring sector, so they are not willing to change anything, cycle continues.
Change what? You're asking for...what exactly? People to provide support for a deprecated platform? That just encourages those companies you're complaining about to continue to use python2 and further splits the ecosystem. No!
> Change what? You're asking for...what exactly? People to provide support for a deprecated platform?
Instead of trying to put words in my mouth and being hostile, try to address my concerns. What I mean is that nobody that is a dev wants to work in a slow boring sector, Which means no work gets done to Python 3 on the vendor side hence, studios like ours keep developing on it.
Which is neither here, nor there. Pre-announcing doesn't give any reason or motive (or funding) for porting large codebases. Many businesses stuck with 2.x will fund 2.x maintenance if the core devs don't do it, and port on their own schedule not on whatever was "pre announced".