Python Lts And Maintenance Cycles Page 6 Ideas Discussions On People use python in many different ways and no solution is going to work for everyone. but what we have today doesn’t reflect the reality of how people are using python. “i need to be updating servers to a recent python release every 3 5 years” is a known factor your organization should be considering when deciding to build mission critical software in python.
Python Lts And Maintenance Cycles Ideas Discussions On Python Org Tl;dr: support for most releases should be shorter (18 36 months) with periodic lts releases supported for 10 to 12 years. this will allow package and tooling maintainers to focus support on a few specific releases. It seems consensus in this thread is that there’s relatively little appetite for python lts (and i agree with this consensus). maybe this thread could now be more productive if we focussed on specific features in tools or packaging you’d like to see?. Let’s say we decide on a 3 year support cycle for interim releases and a 12 year support cycle for lts releases. maybe these are optimistic, but this is for illustrative purposes. We’ve been discussing how support for python is managed and how to ensure packages don’t suddenly pull support in the lts thread in the ideas section one thing that stuck out is python currently makes it quite hard to dig out the support timelines for versions.
Python Lts And Maintenance Cycles Ideas Discussions On Python Org Let’s say we decide on a 3 year support cycle for interim releases and a 12 year support cycle for lts releases. maybe these are optimistic, but this is for illustrative purposes. We’ve been discussing how support for python is managed and how to ensure packages don’t suddenly pull support in the lts thread in the ideas section one thing that stuck out is python currently makes it quite hard to dig out the support timelines for versions. Maptek wants to ensure our customers benefit from newer developments in python and the python ecosystem. likewise, we don’t want to see our customers maintaining an environment to run scripts that require an older version of python. the more time passes, the harder it becomes to upgrade. Python lts and maintenance cycles #python python lts and maintenance cycles #python discuss.python.org 4. Python 3.9 3.12: one and a half years of full support, followed by three and a half years of security fixes python 3.13 and newer: two years of full support, followed by three years of security fixes. Check end of life, release policy and support schedule for python.
Python Lts And Maintenance Cycles Ideas Discussions On Python Org Maptek wants to ensure our customers benefit from newer developments in python and the python ecosystem. likewise, we don’t want to see our customers maintaining an environment to run scripts that require an older version of python. the more time passes, the harder it becomes to upgrade. Python lts and maintenance cycles #python python lts and maintenance cycles #python discuss.python.org 4. Python 3.9 3.12: one and a half years of full support, followed by three and a half years of security fixes python 3.13 and newer: two years of full support, followed by three years of security fixes. Check end of life, release policy and support schedule for python.
Announcing The Playful Python Newsletter Python 3.9 3.12: one and a half years of full support, followed by three and a half years of security fixes python 3.13 and newer: two years of full support, followed by three years of security fixes. Check end of life, release policy and support schedule for python.
Comments are closed.