Skip to content

Remove Python2 from tool versions

Vitaly Slobodin requested to merge vs/drop-python2 into master

Why is this change being made?

Remove Python2 from .tool-versions because of two reasons:

  • Python 2.7 reached the end of its life on January 1st, 2020
  • We don't use it here?

Additionally, attempting to install Python2 fails with the following error:

 Python 2.7.18
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
ERROR: Could not find a version that satisfies the requirement prompt_toolkit<4.0.0,>=3.0.0 (from pgcli->-r /Users/vslobodin/.default-python-packages (line 5)) (from versions: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.8, 0.9, 0.10, 0.11, 0.12, 0.13, 0.14, 0.15, 0.16, 0.17, 0.18, 0.19, 0.20, 0.21, 0.22, 0.23, 0.25, 0.26, 0.28, 0.30, 0.31, 0.32, 0.33, 0.34, 0.35, 0.36, 0.37, 0.38, 0.39, 0.40, 0.41, 0.42, 0.43, 0.44, 0.45, 0.46, 0.47, 0.48, 0.49, 0.50, 0.51, 0.52, 0.53, 0.54, 0.55, 0.56, 0.57, 0.58, 0.59, 0.60, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, 1.0.13, 1.0.14, 1.0.15, 1.0.16, 1.0.17, 1.0.18, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.0.10)
ERROR: No matching distribution found for prompt_toolkit<4.0.0,>=3.0.0 (from pgcli->-r /Users/vslobodin/.default-python-packages (line 5))
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
Collecting docutils
  Using cached docutils-0.18.1-py2.py3-none-any.whl (570 kB)
Collecting gitlint
  Using cached gitlint-0.14.0-py2.py3-none-any.whl (83 kB)
Collecting poetry
  Using cached poetry-1.1.15-py2.py3-none-any.whl (175 kB)
Collecting ranger-fm
  Using cached ranger-fm-1.9.3.tar.gz (226 kB)
Collecting pgcli
  Using cached pgcli-3.0.0.tar.gz (118 kB)
Collecting pynvim
  Using cached pynvim-0.4.3.tar.gz (56 kB)
Collecting qmk
  Using cached qmk-1.0.0-py2.py3-none-any.whl (13 kB)
Requirement already up-to-date: wheel in /Users/vslobodin/.local/share/rtx/installs/python/2.7.18/lib/python2.7/site-packages (from -r /Users/vslobodin/.default-python-packages (line 8)) (0.37.1)
Collecting yamllint
  Using cached yamllint-1.25.0-py2.py3-none-any.whl (60 kB)
Collecting yt-dlp
  Using cached yt_dlp-2021.6.1-py2.py3-none-any.whl (2.1 MB)
Collecting sh==1.12.14; sys_platform != "win32"
  Using cached sh-1.12.14-py2.py3-none-any.whl (38 kB)
Collecting Click==7.0
  Using cached Click-7.0-py2.py3-none-any.whl (81 kB)
Collecting arrow==0.15.5
  Using cached arrow-0.15.5-py2.py3-none-any.whl (46 kB)
Collecting futures<4.0.0,>=3.3.0; python_version >= "2.7" and python_version < "2.8"
  Using cached futures-3.4.0-py2-none-any.whl (16 kB)
Collecting pathlib2<3.0,>=2.3; python_version >= "2.7" and python_version < "2.8"
  Using cached pathlib2-2.3.7.post1-py2.py3-none-any.whl (18 kB)
Collecting tomlkit<1.0.0,>=0.7.0
  Using cached tomlkit-0.7.2-py2.py3-none-any.whl (32 kB)
Collecting poetry-core<1.1.0,>=1.0.7
  Using cached poetry_core-1.0.8-py2.py3-none-any.whl (425 kB)
Collecting packaging<21.0,>=20.4
  Using cached packaging-20.9-py2.py3-none-any.whl (40 kB)
Collecting requests<3.0,>=2.18
  Using cached requests-2.27.1-py2.py3-none-any.whl (63 kB)
Collecting virtualenv<21.0.0,>=20.0.26
  Using cached virtualenv-20.15.1-py2.py3-none-any.whl (10.1 MB)
Collecting typing<4.0,>=3.6; python_version >= "2.7" and python_version < "2.8"
  Using cached typing-3.10.0.0-py2-none-any.whl (26 kB)
Collecting importlib-metadata<2.0.0,>=1.6.0; python_version < "3.8"
  Using cached importlib_metadata-1.7.0-py2.py3-none-any.whl (31 kB)
Collecting functools32<4.0.0,>=3.2.3; python_version >= "2.7" and python_version < "2.8"
  Using cached functools32-3.2.3-2.tar.gz (31 kB)
Collecting pkginfo<2.0,>=1.4
  Using cached pkginfo-1.8.3-py2.py3-none-any.whl (26 kB)
Collecting keyring<19.0.0,>=18.0.1; python_version >= "2.7" and python_version < "2.8"
  Using cached keyring-18.0.1-py2.py3-none-any.whl (35 kB)
Collecting glob2<0.7,>=0.6; python_version >= "2.7" and python_version < "2.8"
  Using cached glob2-0.6.tar.gz (10 kB)
Collecting cachecontrol[filecache]<0.13.0,>=0.12.4; python_version < "3.6"
  Using cached CacheControl-0.12.6-py2.py3-none-any.whl (19 kB)
Collecting cleo<0.9.0,>=0.8.1
  Using cached cleo-0.8.1-py2.py3-none-any.whl (21 kB)
Collecting clikit<0.7.0,>=0.6.2
  Using cached clikit-0.6.2-py2.py3-none-any.whl (91 kB)rtx /Users/vslobodin/.local/share/rtx/installs/python/2.7.18/bin/python exited with non-zero status: exit code 1

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

CHANGEME - add the details saying why, not just what.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Vitaly Slobodin

Merge request reports