Dec-05-2019, 08:51 AM
Hoi Community,
This is a serious last minute plea to keep Python 2.7 alive on LTS please. I work for a company that rely heavily on Python 2.7. The EOL of Python 2.7 is really inconvenient. To soon. It is in fact killing the business. And does not help incubating. There is more time needed for the migration to Python 3. We are a small company and invested in a setup on Python 2.7 because it is the only solution today that can do the job now. We use a lot of good working third party Python products that are not compatible with Python 3. And will not be made compatible by upstream soon.
Now time has come for return on investment there are new investments needed because the Python Community decided that Python 2.7 is going EOL 2020. Python 2.7 is not broken ore insecure ore something. It is just an other good working Python language. PyPy is gone maintain its 2.7 version forever. Unfortunately PyPy is not compatible with our projects. EOL of Python 2.7 is a very bad Python-experience. The way the migration to Python 3 is arranged is not well thought of. With other languages it is just a matter of following the upgrade instructions of the distro. With migration to Python 3 whole good functioning projects need to be rethought of and rebuild. Python 2.7 to Python 3 migration is very painful and gains pretty much nothing.
I understand that developers and big tech are happy with Python 3. For the company I am working for migration to Python 3 is a time consuming and costly hassle. To much need to be done. It is in fact a nightmare. While the projects run secure and superb on Python 2.7. Furthermore Python 2.7 and Python 3 can run at the same time on the same server. For us as users of Python 2.7 there is no value added with Python 3. Just an other technique. Just an other look and feel. Developers say Python 3 is superior. But we do not care. We just want our projects to run. Legacy ore not. And Python 2.7 does the job. No complains what so ever. Python 2.7 does everything for us we need. Stable and secure. Thanks to the Python Community. Till now.
We only plea for Long Time Support for Python 2.7. by the Python Community so we have secure Python 2.7 on the server after 2020 from a trusted supplier. If the Python Community keeps Python 2.7 alive, the distro’s will follow. Helping a lot of Python users out of migration troubles. There is no objective reason to EOL Python 2.7 2020. It is just a decision made. Support can be extended. And compensates the lack of backward compatibility. A little effort to make a lot of projects and hosters and admins happy. If PyPy can maintain its 2.7 version forever and develop its other versions. The Python Community can. Bet that LTS of Python 2.7 by the Python Community will not hurt development on Python 3. Think that more projects can survive that way which benefits the Python Community and diversity in general. It is destruction of capital to EOL Python 2.7.
In the name of many unheard Python users: please stop trolling us with the EOL of Python 2.7.
Thank you in advance.
J.
This is a serious last minute plea to keep Python 2.7 alive on LTS please. I work for a company that rely heavily on Python 2.7. The EOL of Python 2.7 is really inconvenient. To soon. It is in fact killing the business. And does not help incubating. There is more time needed for the migration to Python 3. We are a small company and invested in a setup on Python 2.7 because it is the only solution today that can do the job now. We use a lot of good working third party Python products that are not compatible with Python 3. And will not be made compatible by upstream soon.
Now time has come for return on investment there are new investments needed because the Python Community decided that Python 2.7 is going EOL 2020. Python 2.7 is not broken ore insecure ore something. It is just an other good working Python language. PyPy is gone maintain its 2.7 version forever. Unfortunately PyPy is not compatible with our projects. EOL of Python 2.7 is a very bad Python-experience. The way the migration to Python 3 is arranged is not well thought of. With other languages it is just a matter of following the upgrade instructions of the distro. With migration to Python 3 whole good functioning projects need to be rethought of and rebuild. Python 2.7 to Python 3 migration is very painful and gains pretty much nothing.
I understand that developers and big tech are happy with Python 3. For the company I am working for migration to Python 3 is a time consuming and costly hassle. To much need to be done. It is in fact a nightmare. While the projects run secure and superb on Python 2.7. Furthermore Python 2.7 and Python 3 can run at the same time on the same server. For us as users of Python 2.7 there is no value added with Python 3. Just an other technique. Just an other look and feel. Developers say Python 3 is superior. But we do not care. We just want our projects to run. Legacy ore not. And Python 2.7 does the job. No complains what so ever. Python 2.7 does everything for us we need. Stable and secure. Thanks to the Python Community. Till now.
We only plea for Long Time Support for Python 2.7. by the Python Community so we have secure Python 2.7 on the server after 2020 from a trusted supplier. If the Python Community keeps Python 2.7 alive, the distro’s will follow. Helping a lot of Python users out of migration troubles. There is no objective reason to EOL Python 2.7 2020. It is just a decision made. Support can be extended. And compensates the lack of backward compatibility. A little effort to make a lot of projects and hosters and admins happy. If PyPy can maintain its 2.7 version forever and develop its other versions. The Python Community can. Bet that LTS of Python 2.7 by the Python Community will not hurt development on Python 3. Think that more projects can survive that way which benefits the Python Community and diversity in general. It is destruction of capital to EOL Python 2.7.
In the name of many unheard Python users: please stop trolling us with the EOL of Python 2.7.
Thank you in advance.
J.