https://bugzilla.redhat.com/show_bug.cgi?id=1091657
--- Comment #2 from Orion Poplawski <orion(a)cora.nwra.com> ---
(In reply to Bohuslav "Slavek" Kabrda from comment #1)
Few general comments/questions:
- Does introducing python34 mean that we will be creating python34-foo
packages for EPEL?
I think that has to be the case.
- Does introducing python34 mean that your intention in future is to
also
maintain python35, python36, ...?
Not particularly. If sometime down the road, python34 has crusted over too
much there might be a push to move to a new python3X.
I'm not opposed to this, but we will probably need to standardize how
extension packages should be packaged for python3X in EPEL. E.g. assuming we
have python34 and python35, does that mean that we'll also need
python3{4,5}-setuptools and the same for any other package? After several
years, we could end up with several huge stacks of unmaintained packages and
I have to admit I really don't like the idea. What are your thoughts on this?
Yeah, this could be a big risk. It's probably a good idea to reach out to more
EL7 stakeholders and trying to build a consensus plan for pytho3 in EL7.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component