On 4/26/23 18:16, John Snow wrote:

     > - I am ambivalent about keeping --enable/--disable-pypi in the first
     > committed patchset, but in any case I would move patches 16 and 20
     > before patch 15

I might be stubborn but I think I want to keep it in for now. If it needs redesigned to fit with the other flags you want to add, I think that's OK.

if we vendor the whl directly in qemu.git we won't need PyPI for meson, but it's still useful for Sphinx so I think I'm still leaning towards keeping it.

Yes, it's definitely useful. It's just that unifying $python with sphinx-build's interpreter is as a separate (and earlier) step than introducing PyPI.

I'll try to refactor to keep it at the tail end of the series.

Cool, thanks.

    Just one extra thing, since we're changing so much of Python handling
    and since the code is written, I would keep the Debian 10 workarounds
    for now, and only drop them after we drop support for 3.6.


This series was written assuming we get to drop 3.6 as a prereq. Is that not the case?

Or did you mean to write 3.7 there?

Yes, 3.7.

Paolo


Reply via email to