On 9/6/18 5:32 PM, Miro Hrončok wrote:
In Fedora, we advertise "all the Pythons" are available and developers
may use them with venv, virtualenv, tox.
https://developer.fedoraproject.org/tech/languages/python/multiple-pythons.html
Two of the interpreters we ship are quite problematic in this regard.
### Python 2.6
- virtualenv 16.x dropped support for 2.6 and we dirty patched it back
- tox 3 dropped support for 2.6
- pip/setuptools dropped support for 2.6 and our patched virtualenv
uses an older version of pip and setuptools to make work
However, I know there are developers who use Python 2.6 in Fedora
(namely because their software maintains RHEL 6 compatibility).
I propose that we indicate on Fedora Developer Portal that Python 2.6 is
provided as is and that it may not work with virtualenv/tox. We maintain
the current patch of virtualenv at least for the lifetime of Fedora 29,
but if an upgrade of virtualenv is done, we ditch that patch from Fedora
30+.
We also mark it deprecated and schedule the removal for EPEL 6 EOL
(AFAIK late 2020).
### Jython
- virtualenv somehow works but is not officially supported
- pip is not supported and has hesisenbugs
I know nobody who uses Jython with virtualenv and tox.
I propose that we indicate on Fedora Developer Portal that Jython is
provided as is and that it may not work with virtualenv/tox.
(No scheduled removal.)
Thoughts?
Sounds reasonable. I just think before any code changes, we should also
add a section to the portal on how to use virtualenv/tox with the old
versions. The workaround is not pretty, but people shouldn't need to
rediscover it.
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
