----- Original Message -----
Is the EPIC proposal totally dead? It seems like that would be a
and more general solution to this problem (not wanting to ship a Python
3.x stack for 10 years).
I'm not sure about that, but I think we can align python3 in epel with EPIC even if
EPIC is introduced later on.
Personally I am not looking forward to maintaining more branches
(sub-)packages for every python3X-*.
The way I see it, we will only maintain a single python3X-* subpackage most of the time;
then, when python3X+1 is released, we will maintain two subpackages for a short period of
time, until python3X is retired.
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
epel-devel mailing list