On Thu, 2019-05-02 at 10:26 -0700, Kevin Fenzi wrote: > Sorry this is all so confusing. ;( Life can be complicated at times! :) I admit that the way this Python 3.4 => 3.6 update worked suprised me. I have binary packages that depend on several python34-* packages. The update broke those in a couple of ways; not only by the disappearance of the pycurl and mysql pieces, but by the fact that '/usr/bin/python3' got changed to point to '/usr/bin/python3.6' rather than '/usr/bin/python3.4'. What is best practice for specifying Python dependencies so that they will survive this sort of thing? Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------| _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
