On 28. 07. 21 1:19, Neal Gompa wrote:
3) In Fedora, various Python interpreters use pip/setuptools/wheel wheels from
/usr/share/python-wheels or bundle their own wheel when the "general" ones are
too new to work with old Pythons. Given the differences of life cycle of RHEL
and Fedora, we plan to use wheels from /usr/share/python3.X-wheels instead (and
have the possibility to build newer versions of pip/setuptools/wheel wheels for
each newer Python version we introduce to RHEL 9). RHEL 8 already partially
does that for Python 3.8+, but in RHEL 9, we want to do this from the
beginning. I intent to do the rpm-macros-groundwork for this in Fedora, but we
might need to explicitly not make this change in ELN to preserve Rawhide/ELN
builds compatibility.
https://bugzilla.redhat.com/show_bug.cgi?id=1982668
Aren't wheels fully versioned themselves? Why do you need the wheel
directory itself to be versioned?
(This entire answer applies to pure-python wheels only, which is what we ship
anyway.)
They include the version of the project, not version of the Python interpreter.
They only declare Python 2/3 compatibility in the name:
$ ls -1 /usr/share/python-wheels/
pip-20.2.2-py2.py3-none-any.whl
setuptools-49.1.3-py3-none-any.whl
wheel-0.34.2-py2.py3-none-any.whl
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
