Python 2 End of Life Survey Results

Python 2 End of Life Survey Results

Python 2 End of Life Survey Results

ActiveState surveyed a wide array of Python users to better understand how they have been preparing for the End of Life (EOL) of Python 2, which officially occurred on January 1, 2020.

Readers should find the survey data useful when it comes to understanding the challenges, strategies and tactics for solving their own Python 2 EOL pains.

Download the survey results, or contact us if you would like the full survey data.

Do you have a plan in place? ActiveState can help by providing regular security updates and a custom Python 2 support plan.

Further Analysis on Python 2 EOL

Report Card – Is the Industry Ready? – ActiveState Blog

Finding replacement packages was cited as the top concern in our survey. For example, some respondents reported a dependency on a commercial package that had yet to provide support for Python 3 as the key blocker in their migration efforts. Others are still in the process of ramping up their skills and preparing key systems, like test suites.

Report Card - Is the Industry Ready? - ActiveState Blog

Sunsetting Python 2 – Python Software Foundation

We are volunteers who make and take care of the Python programming language. We have decided that January 1, 2020, was the day that we sunset Python 2. That means that we will not improve it anymore after that day, even if someone finds a security problem in it. You should upgrade to Python 3 as soon as you can.

python software foundation logo

Think App Updates Suck? Try Upgrading a Programming Language – Wired

“I don’t think anyone says ‘I don’t want to update,'” says Jacqueline Kazil, a member of the Python Foundation board. “But maintenance like this takes time. And the people responsible for doing the update aren’t working on adding new features that are generally recognized as bringing new business revenue. But if you ignore ongoing maintenance, eventually it will cost you a lot more than the new features would have added.”

Wired Logo

Time to Shed Python 2 – National Cyber Security Centre (NCSC)

The WannaCry ransomware provides a classic example of what can happen if you run unsupported software. It infected more than 230,000 computers, causing major disruption around the globe. By making the decision to continue using Python 2 past its end of life, you are accepting all the risks that come with using unsupported software…

Time to shed Python 2 - National Cyber Security Centre (NCSC)

Python 2 Support Past EOL

Continued use of Python 2 leaves you exposed to security vulnerabilities. If you still have software dependent on Python 2, ActiveState gives you a safety net, freeing up your resources to move to Python 3.


Python 2 support includes:

Security patches for Python 2 standard and 3rd-party libraries, helping you stay secure and compliant with PCI-DSS, FedRAMP and other regulations.
Patches and updates delivered within 2-3 months – critical patches within 30 days.
Service-Level Agreements (SLAs) with guaranteed support for critical and high CVE’s (common vulnerabilities and exposures)

Python 2 EOL Risk Assessment

ActiveState provides continuing support and security updates for Python 2. Speak with one of our Python experts today.

Trusted by Industry Leaders Worldwide

Capital One logo grayscale

Recent Posts

Scroll to Top