Bug 1275417
Summary: | Build aiohttp for epel7 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Pierre-YvesChibon <pingou> |
Component: | python-aiohttp | Assignee: | Fabian Affolter <mail> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel7 | CC: | carl, code, jakub.ruzicka, mail, nicki |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-01-30 14:54:48 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pierre-YvesChibon
2015-10-26 20:53:45 UTC
aiohttp seems to be Py3 only. And epel7 has python3 now so if we can get the dependencies built in epel7, we will be able to build aiohttp as well :) (In reply to Pierre-YvesChibon from comment #2) > And epel7 has python3 now so if we can get the dependencies built in epel7, > we will be able to build aiohttp as well :) IIRC there is 3.4, which doesn't have asyncio support. aiohttp works on Python 3.4. The new await/async def syntax is optional. https://aiohttp.readthedocs.io/en/stable/#dependencies says: "Python 3.4.2+" Current state as of February 2021: - Python 3.6 is available - aiohttp version 3.6.x can be built on CentOS7 with only slight modifications (dependency names) from EPEL8 spec - dependencies of aiohttp would need to be packaged for EPEL7 as well At a first glance, I don't see any blocking issue, but I didn't explore the dependency chain thoroughly. I’m not the primary maintainer here, but I’ve done the last several python-aiohttp updates in Fedora and EPEL9. - The current version of aiohttp has dependencies that are difficult to package or update for EPEL7. Even keeping EPEL8 up to date has not been practical. - Recent releases of aiohttp have contained significant security fixes, so packaging an older release seems unwise. - EPEL7 reaches its end-of-life this year anyway. Considering the above, I’m sorry that this never worked out, but I think it’s safe to say that an EPEL7 build will not happen. Anyone who disagrees may feel free to reopen the bug. |