On Wed, Jul 3, 2024 at 5:25 PM John Snow <js...@redhat.com> wrote: > To be clear I mean offline, isolated RPM builds under RHEL9 where I don't > think we can utilize PyPI at all; and vendoring Sphinx is I think not a > practical option due to the number of dependencies and non-pure Python deps. > > It's not a problem for developer workflow, just downstream packaging.
Agreed, switching to PyPI packages is not something that should be done lightly---only after the platform Python is EOL, and only if there are benefits for QEMU to require 3.9 (like there were for 3.7). In that case, downstream could still package QEMU but they'd have to build python39-sphinx or something like that. Paolo > Luckily OpenSUSE offers newer Sphinx, but RHEL doesn't yet. Maybe that can be > rectified eventually - possibly after 3.8 is EOL and there is increased > demand for newer Python packages to be made available in RHEL... but not yet, > today. > >> >> >> Paolo >> > > Thanks for the ack O:-)
