python2.7 will be removed from the python-versions on June 19

Breaking changes

Hello everyone. The Python 2.7.x will be removed from python-versions and it won't be possible to set up Python 2.7.x by setup-python.

The motivation for the changes

Python2.7 is not supported since January 1, 2020.

@dmitry-shibanov

Hi @dmitry-shibanov - do you have any recommended ways to mitigate this for those of us that cannot remove usage of Python 2.7 from our Github Actions before the June 19th deadline?

@dmitry-shibanov

@dmitry-shibanov

February 2020: GitHub said they'd remove 2.7 from Actions. https://github.blog/changelog/2020-02-27-github-actions-breaking-change-python-2-being-removed-from-all-virtual-environments/
March 2020: GitHub said they'd exceptionally keep 2.7 longer. Effect of python 2 sunset on setup-python #63 (comment)
November 2022: GitHub removed 2.7 from Actions.
December 2022: GitHub added 2.7 back to Actions.
April 2023: GitHub announced they'll be removing 2.7 in May 2023.

It has already been delayed.

@konradpabjan I hope this can be cancelled like the previous times. I think there will be customer backslash again which would not be justified.

There is no point in removing it.

Linux Distros like Ubuntu 20.04 which contain Python2.7 support Python 2.7 for many many years to come. Canonical will maintain it until April 2025, and it will have emergency security updates in 20.04 until April 2030. Similar for Red Hat and SUSE.

We started hitting this today already (1 June 2023), leading to:

Error: Version 2.7 with arch x64 not found

Support for Python 2.7 is deprecated in our project already, so we'll just stop testing on top of Python 2.7 and not lose sleep over it, but it would be nice if there's a documented/recommended alternative for people that do still want to keep testing on top of Python 2.7 in the near future.

There's a community-maintained Dockerfile in the works: actions/runner-images#7401 (comment)

tests.yml: stop testing Python 2.7

Guys, do we have a suggested workaround? This is a huge deal for us - whole project depends on python 2 so we would not be able to deploy anything. If anyone has an idea, please help :)

To anyone concerned:
You can continue using github-hosted runners with python2.7 by running the job inside a container.
e.g. I used python:2.7-buster image and everything works out just fine.

No need to use setup-python or be dependent of runner-images anymore.

If you don't need 2.7 for windows, you could use my custom action MatteoH2O1999/setup-python.
This action tries to build from source all Python versions that actions/setup-python does not support.
It also allows to cache built versions so that after the first run, installation time is really low.
For an example of a run see this workflow.

Windows support is in the works but no ETA (note that for Windows it will still allow for versions that are supported by 'actions/setup-python' to successfully complete).

@tzortzispanagiotis

To anyone concerned: You can continue using github-hosted runners with python2.7 by running the job inside a container. e.g. I used python:2.7-buster image and everything works out just fine.

Hello @tzortzispanagiotis, could you please provide an example for this? 🙏

Thanks in advance.

@dimitrisr

Hello @dimitrisr,

In order to overcome this I modified:

runs-on: ubuntu-20.04

to

runs-on: ubuntu-20.04
    container:
      image: python:2.7.18-buster

So that the job is run using a github-hosted runner, but inside the python2.7-buster container, which has set up python2.7

Then I started running the pipeline and started fixing everything that was broken (because the container does not have things as sudo, so you have to install it with a command)

Also, If your CI pipeline has other services (e.g. mysql) that run inside a container, now that the whole job is running inside a container, the service container is accessible not through localhost (127.0.0.1), but through the service name.

I hope I was helpful!

@tzortzispanagiotis

Thank you @tzortzispanagiotis, this was really helpful! I was able to run the actions successfully :)

.github/workflows/main.yml: Py2.7: Use a wrapper for setup-python

test: don't run tests on python 2.7

CI: python 2.7 tests needs to run in a container (#5174)

💚 Fix-ci(ci.yml): remove Python 2.7.x from the CI matrix

Add support for parsing the Path Attribute: BGP Prefix-SID (Type 40) …

Fix Github Actions (#347)

Drop testing with Python 2.7

CI: remove 2.7 support to fix build

fix(ci): the support for python 2.7 was removed on June 19, 2023

Update Python versions in GitHub actions

Update GitHub actions

Tweak Python versions in CI (#90)

Drop testing of Python 2.7

Work around py27 unsupported on GH actions

Navigation Menu

Repository navigation

python2.7 will be removed from the python-versions on June 19 #672

Breaking changes

The motivation for the changes

225 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

python2.7 will be removed from the python-versions on June 19 #672

Description

Breaking changes

The motivation for the changes

Activity

rtibbles commented on May 30, 2023

bernhardkaindl commented on May 30, 2023

boegel commented on Jun 1, 2023

hugovk commented on Jun 1, 2023

tzortzispanagiotis commented on Jun 7, 2023

tzortzispanagiotis commented on Jun 8, 2023

MatteoH2O1999 commented on Jun 8, 2023

dimitrisr commented on Jun 13, 2023

tzortzispanagiotis commented on Jun 13, 2023

dimitrisr commented on Jun 13, 2023

225 remaining items

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions