Non of the argument for the EOL of Python 2 are valid
Hey, glad my post was too much for you to read and point out exactly what was wrong.
We are now forced to pay developers for upgrading instead for enhancing our Python 2 projects. Money can only spend once. To make money to pay developers, we need enhancements and (more) hosting of our Python 2 projects instead of upgrading tot Python 3.
I think I already indicated earlier that you had almost a decade to budget in costs for Python 3 upgrades (or simply changed your coding style to be prepared for them, which costs just about nothing) when charging your customers. If you didn't do this, that's your problem, not Python's.
It's hard to imagine that a poor decision has caused a problem that is now out of your control. You're right, the money can only be spent once, and it should have been spent on preparing to update to Python 3 so that your business could continue to function in the future. It may not have seemed "essential" at the time, but as you realize now, you can not force someone to do work they do not want to do such as continue to work on Python2, just like the Python developers could not force you to update your code.
Your lived reality is that you have a problem now, but if you won't acknowledge that your refusal to prepare for the future contributed to the problem, you're not going to get much sympathy here. Trying to cite "business" as an emphasis actually undermines any point you try to make, as business is a "do or die" environment with no consideration to the welfare of companies that go under. What you should have "done" is update to Python3, because now you're facing the prospect of the company "dying."
The EOL of Python 2 is a form of unfair competition
EoLing products, particularly when the EoL date is set in advance so you can make plans, is not a form of unfair competition.
Let us look upon the
Python 2 license and despair:
* Provided on an "as is" basis
* No warranty
* No merchantability
* No fitness for any particular purpose
* No partnership
* No permission to use the trademark (aka "Python")
Python2 had no obligation to you. You chose Python 2 at your own risk. Your only exit hatch is that you can do the work of keeping Python2 alive
yourself.
Never seen something like this in the more than 20 years we use FOS.
20 years, you say?
Let's see... You must be used to this kind of disappointment already, when you realized that FreeBSD stopped providing security fixes, packages and ports that would work on version 4.0.