Skip to content
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.

Python 2 end-of-life in 2020 #126

Open
vitaly-zdanevich opened this issue Nov 6, 2019 · 2 comments
Open

Python 2 end-of-life in 2020 #126

vitaly-zdanevich opened this issue Nov 6, 2019 · 2 comments

Comments

@vitaly-zdanevich
Copy link

https://www.infoworld.com/article/3365221/python-2-end-of-life-how-to-survive-the-end-of-python-2.html

@vitaly-zdanevich
Copy link
Author

Still not published for Gentoo, but today through the eselect news read I got this broadcast message:

2020-02-07-python-2-7-eol
Title Python 2.7 went EOL
Author Michał Górny [email protected]
Posted 2020-02-07
Revision 1

Python 2.7 has reached its end-of-life by 2019-12-31. Python package
upstreams have started removing Python 2 compatibility code from their
packages more aggressively. This includes common dependencies such as
dev-python/pytest, dev-python/setuptools and dev-python/sphinx. While
we realize that many packages are still dependent on Python 2, providing
full support for it exceeds our maintenance capabilities.

Upstream is planning to make one more release of dev-lang/python:2.7
in April 2020. We are going to continue maintaining and patching
the interpreter for as long as it is feasible, most likely even after
all Python 2 packages are gone from Gentoo.

At the same time, we are actively working towards switching
the distribution to Python 3. Whenever possible, we are removing
Python 2 support from packages. It will remain available for
the packages missing Python 3 compatibility and their dependencies
for some more time. However, packages that have little chances of being
ported will eventually be removed.

If you are still using Python 2 for your projects, we strongly recommend
you to migrate away. For the time being, it is preferable to use
dev-python/virtualenv or a similar solution rather than ebuilds,
to install the dependencies for your projects locally.

Regular Gentoo systems will be migrated off Python 2 gracefully. It may
be necessary to use --changed-deps or a similar option during system
upgrades whenever they become blocked by Python 2 packages installed
earlier.

If you wish to remove Python 2.7 entirely sooner, you can try removing
python2_7 from PYTHON_TARGETS. However, this will require adding
explicit package.use entries if some of the installed packages still
require Python 2.

Note that package.use entries are not necessary for packages that
support one implementation only (i.e. do not support Python 3 at all).

I am afraid that this is not possible to have Geeknote in Portage (Gentoo repository) for end-of-lifed Python 2. @jeffkowalski, is it possible to migrate to Python 3? This is not only about Gentoo.

@kurokirasama
Copy link

so we can't install it on 20.04?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants