Hello Pythonistas.
The virtualenv version in Fedora is currently stuck at 20.21.1 (April 2023).
This is because version 20.22+ dropped support for Python 2.7 and 3.6 virtual environments.
Now when Python 2.7 was retired via https://fedoraproject.org/wiki/Changes/RetirePython2.7 the only difference is Python 3.6.
If we upgrade virtualenv, developers targeting Python 3.6 (e.g. RHEL 8 platform Python) can use `python3.6 -m venv` to create Python 3.6 virtual environments. Developers using tox can follow https://tox.wiki/en/4.18.0/faq.html#testing-end-of-life-python-versions
I propose we bite the bullet and update virtualenv to the latest version in Fedora 42+.
On Mon, Aug 26, 2024 at 6:11 AM Miro Hrončok mhroncok@redhat.com wrote:
Hello Pythonistas.
The virtualenv version in Fedora is currently stuck at 20.21.1 (April 2023).
This is because version 20.22+ dropped support for Python 2.7 and 3.6 virtual environments.
Now when Python 2.7 was retired via https://fedoraproject.org/wiki/Changes/RetirePython2.7 the only difference is Python 3.6.
If we upgrade virtualenv, developers targeting Python 3.6 (e.g. RHEL 8 platform Python) can use `python3.6 -m venv` to create Python 3.6 virtual environments. Developers using tox can follow https://tox.wiki/en/4.18.0/faq.html#testing-end-of-life-python-versions
I propose we bite the bullet and update virtualenv to the latest version in Fedora 42+.
Why not do it for 41? The reason we didn't do it before was because of Python 2.7, which we dropped now.
On 26. 08. 24 12:58, Neal Gompa wrote:
On Mon, Aug 26, 2024 at 6:11 AM Miro Hrončok mhroncok@redhat.com wrote:
Hello Pythonistas.
The virtualenv version in Fedora is currently stuck at 20.21.1 (April 2023).
This is because version 20.22+ dropped support for Python 2.7 and 3.6 virtual environments.
Now when Python 2.7 was retired via https://fedoraproject.org/wiki/Changes/RetirePython2.7 the only difference is Python 3.6.
If we upgrade virtualenv, developers targeting Python 3.6 (e.g. RHEL 8 platform Python) can use `python3.6 -m venv` to create Python 3.6 virtual environments. Developers using tox can follow https://tox.wiki/en/4.18.0/faq.html#testing-end-of-life-python-versions
I propose we bite the bullet and update virtualenv to the latest version in Fedora 42+.
Why not do it for 41? The reason we didn't do it before was because of Python 2.7, which we dropped now.
Because I think kit's too late in the F41 dev cycle to introduce such change and I am willing to keep backporting fixes to old virtualenv in Fedora 41.
The reason was both 2.7 and 3.6. And as of now, 2.7 is still in Fedora 41.
On Mon, Aug 26, 2024 at 01:08:35PM +0200, Miro Hrončok wrote:
On 26. 08. 24 12:58, Neal Gompa wrote:
On Mon, Aug 26, 2024 at 6:11 AM Miro Hrončok mhroncok@redhat.com wrote:
Hello Pythonistas.
The virtualenv version in Fedora is currently stuck at 20.21.1 (April 2023).
This is because version 20.22+ dropped support for Python 2.7 and 3.6 virtual environments.
Now when Python 2.7 was retired via https://fedoraproject.org/wiki/Changes/RetirePython2.7 the only difference is Python 3.6.
If we upgrade virtualenv, developers targeting Python 3.6 (e.g. RHEL 8 platform Python) can use `python3.6 -m venv` to create Python 3.6 virtual environments. Developers using tox can follow https://tox.wiki/en/4.18.0/faq.html#testing-end-of-life-python-versions
I propose we bite the bullet and update virtualenv to the latest version in Fedora 42+.
Why not do it for 41? The reason we didn't do it before was because of Python 2.7, which we dropped now.
Because I think kit's too late in the F41 dev cycle to introduce such change and I am willing to keep backporting fixes to old virtualenv in Fedora 41.
The reason was both 2.7 and 3.6. And as of now, 2.7 is still in Fedora 41.
+1 to doing this just in rawhide now.
Zbyszek
python-devel@lists.fedoraproject.org
-
Miro Hrončok -
Neal Gompa -
Zbigniew Jędrzejewski-Szmek