Bug 1602347 - python-virtualenv update to 16.0 broke python 2.6 and therefore esting with tox against python 2.6 on Fedora 28
Summary: python-virtualenv update to 16.0 broke python 2.6 and therefore esting with t...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-virtualenv
Version: 28
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-18 09:08 UTC by Till Maas
Modified: 2020-02-21 19:43 UTC (History)
10 users (show)

Fixed In Version: python-virtualenv-16.0.0-4.fc28 python-virtualenv-16.0.0-4.fc27
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-30 18:26:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Till Maas 2018-07-18 09:08:50 UTC
Description of problem:
Fedora advertises that developers can use Fedora to test with tox against python 2.6 at https://fedoralovespython.org/ and https://developer.fedoraproject.org/tech/languages/python/multiple-pythons.html but the update to virtualenv 16.0 broke python 2.6. support.

Version-Release number of selected component (if applicable):
python3-virtualenv-16.0.0-1.fc28.noarch

How reproducible:
always

Steps to Reproduce:
1. dnf install tox
2. cat > 'tox.ini' <<EOF
[tox]
envlist = py26
skipsdist = True

[testenv:py26]
basepython = python2.6
EOF

3. tox

Actual results:
Error:
ERROR: actionid: py26
msg: getenv
cmdargs: ['/usr/bin/python3', '-m', 'virtualenv', '--python', '/usr/bin/python2.6', 'py26']

ERROR: None
ERROR: this script requires Python 2.7 or greater.
Running virtualenv with interpreter /usr/bin/python2.6



Expected results:
should continue to work as it did when Fedora 28 was released with virtualenv 15.0

Additional info:
maybe a python26-virtualenv compat pkg could be introduced and virtualenv or tox be patched to use the code from there. Otherwise it should be properly announced and coordinated that the support for Python 2.6 and tox on Fedora was dropped or at least announced that a dnf downgrade python3-virtualenv is needed.

Comment 1 Miro Hrončok 2018-07-18 11:02:36 UTC
Oh no. Ok, let's check what changed in virtualenv, whether we can bring the support back.

Comment 2 Miro Hrončok 2018-07-18 11:19:45 UTC
Till, could you please try with:

https://src.fedoraproject.org/rpms/python-virtualenv/pull-request/2

Comment 3 Miro Hrončok 2018-07-18 11:25:52 UTC
Nope, that seems incomplete.

Comment 4 Miro Hrončok 2018-07-18 11:50:08 UTC
Amended. It works for me, please test it and merge when ready, I gotta go offline.

https://src.fedoraproject.org/rpms/python-virtualenv/pull-request/2

Comment 5 Till Maas 2018-07-18 15:10:18 UTC
I reported in the PR that it is no working. Not sure why it worked for you, I tried the PoC I published above and it fails when calling "tox --recreate" (the --recreate is better to test since otherwise the cache might mask the error).

Comment 6 Fedora Update System 2018-07-24 14:53:59 UTC
python-virtualenv-16.0.0-4.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-1a22e606a6

Comment 7 Fedora Update System 2018-07-24 15:08:19 UTC
python-virtualenv-16.0.0-4.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2c7e519668

Comment 8 Fedora Update System 2018-07-25 19:12:40 UTC
python-virtualenv-16.0.0-4.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-1a22e606a6

Comment 9 Fedora Update System 2018-07-25 19:35:50 UTC
python-virtualenv-16.0.0-4.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2c7e519668

Comment 10 Fedora Update System 2018-07-26 12:00:08 UTC
python-virtualenv-16.0.0-4.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-1a22e606a6

Comment 11 Fedora Update System 2018-07-30 18:26:38 UTC
python-virtualenv-16.0.0-4.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2018-08-02 15:39:46 UTC
python-virtualenv-16.0.0-4.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 13 Adam Williamson 2020-02-21 17:20:19 UTC
Not sure how much anyone cares at this point, but this problem is back, you cannot run `tox` with the `py26` env in Fedora 32 (probably also Fedora 31, I think). This is kind of a problem if you still care about EL 6, which doesn't go EOL until November...

Comment 14 Miro Hrončok 2020-02-21 19:43:02 UTC
This is known and documented. The problem here was that 2.6 support was accidentally dropped from a stable release, hence we patched it back, but decided to only support that to a certain point. That point turned out to be Fedora 30.

Since Fedora 31, we don't support Python 2.6 from (the packaged version of) virtualenv/tox. Workaround exists.

https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/UNO2CTFUT6K7RE3J2JJGUC4JXSFS3RUG/

https://developer.fedoraproject.org/tech/languages/python/multiple-pythons.html



See also slightly related https://fedoraproject.org/wiki/Changes/RetirePython26 (Fedora 33 approved change).


Note You need to log in before you can comment on or make changes to this bug.