On Fri, 10 Feb 2023 at 17:55, John Snow <jsnow@redhat.com> wrote:
> (The problem with just allowing sphinx to be a black box and
> continuing to happily use the 3.6-based versions is that we are
> using QAPIDoc extensions from our own codebase, which would lock
> those to 3.6. A big motivator for Markus is dropping some 3.6
> kludges we're carrying for qapi, so I looked to the opposite
> solution - nudging Sphinx forward instead.)
Mmm. Where on the pain spectrum does "allow python 3.8
because CentosOS ships that, except that where our python
code gets run via Sphinx that part of the codebase must
retain 3.6 compatibility" sit ?
As far as the build system is concerned no changes are required, however Python 3.7 support was requested by Markus for scripts/qapi/ for quite some time. So it would not be painful to implement but it would remove most of the benefits of dropping support for 3.6.
Paolo