Dne 19. 05. 20 v 14:03 Richard Shaw napsal(a):
> Because Qt 5.13.x / PySide2 5.13.x is NOT compatible with Python 3.8. But instead of asking ourselves, "should we push
> in the VERY latest Python and hope it's ok?", we just patch the build system to accept it anyway and hope for the best.
>
> Qt (et all) is a pretty organized upstream, so when asked about Python 3.8 support in 5.13.x, they said, "Nope. Wait for
> 5.14.x."
>
BTW this is scholar example of use-case for Modularity.
Maybe if each python module is made parallel installable AND each app which uses python is tied to using that exact version of python versus python3. Otherwise you could end up with QT apps needing python3.6, XYZ (let us say TeX) apps needing python3.8 and dnf needing python3.9 and ONLY ONE OF THESE CAN BE INSTALLED. And since dnf needs to be there.. I guess you would have no QT or whatever.
If each of them have been patched to be parallel installable and the apps have been patched to call python3.8 versus python3.. the only thing modularity is helping is with giving a list of builds orders to make ti work correctly. It also adds to each of those groups the maintenance of those python modules because the python team has just enough people to maintain 1 module. Not 2, not 3, not one for every old version of python3.
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
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/devel@lists.fedoraproject.org