On Wed, 11 Dec 2019 at 17:23, Fred Gleason <fredg@xxxxxxxxxxxxxxxxxx> wrote: > > On Dec 11, 2019, at 12:50, Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > > The issue is that most 'users' of the language do not see a difference > between the 2. When they say python3x they mean > python3x+whatever-bits-i-needed. So as soon as you put in the > interpreter.. then comes the 'why isn't python37-x there? etc etc' > > > IIRC, that is exactly what happened with the 3.4 => 3.6 transition. What made that particularly painful for me was that the 3.4 versions of many of the dependent bits suddenly went away, to be *replaced* (rather than augmented) by 3.6 ones. This caused major disruption in a number of projects that I maintain that had formal dependencies on the 3.4 bits. > > Will this same thing happen to the 3.6 bits if we add 3.7? If so, then I would strongly oppose making the addition. Having packages spontaneously disappear seems to contradict the whole point of having an ‘Enterprise’ distro. I want to correct one thing: EPEL is not an Enterprise repository. It is a nearly complete volunteer effort and things will add and disappear over time as volunteers come in and out. We try to make it stable and useful but we do not guarantee/promise/etc any Enterprise level 'support'. If you are needing that then I would contract out for it with someone who can do that kind of work... or come up with techniques to mitigate changes that will occur in EPEL. -- Stephen J Smoogen. _______________________________________________ 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
