On Wed, Feb 18, 2026 at 4:34 PM John Snow <[email protected]> wrote: > > Hello! > > This series drops the in-tree version of our python-qemu-qmp package > ("qemu.qmp") in favor of the version hosted on PyPI, whose repository is > located at https://gitlab.com/qemu-project/python-qemu-qmp. > > GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2335222126 > > The major effects of this patch series are: > > 1. qemu.qmp and the python/ directory will be installed to the > configure-time venv (build/pyvenv) by default. > 2. qemu.qmp will be installed from PyPI or vendored packages instead of > being utilized directly from the qemu.git tree. > 3. "make check-venv" is removed as it is no longer needed. > 4. functional test dependencies are installed as-needed when running > those tests. > 5. Unfortunately, python3-wheel and python3-setuptools are now required > on the host system if tests are to be executed and >= Python 3.13 is > used. > 6. An awful lot of deleted lines of code, and a lot fewer headaches > managing two nearly-identical copies of this source code. O:-) > > v8: > > - lcitool update patch(es): > - Fixed netbsd VM test > - Half-fixed Haiku VM test; > test fails now for reasons other than this patchset > - New patch; added compatibility for iotests ./check to run outside of > the venv, while tests will still run inside the venv, as a > transitional lubricant for block maintainer workflow (Thanks, Kevin!) > - I really think this is it, any other small change requests I think > should be addressed as follow-up patches at this point. Otherwise, > it's going to get out of hand... > > Note 1: The lcitool upgrade causes a failure in check-rust-tools-nightly > (which is allowed to fail), and a separate standalone fix for this issue > has been sent as > https://patchew.org/QEMU/[email protected]/ > > Note 2: This series does not fix the currently failing check-python-tox > test (also allowed to fail), which is fixed separately in > https://patchew.org/QEMU/[email protected]/ > > Note 3: This series works around, but does not fix, the fact that we are > still utilizing Debian 11 for our CI infrastructure. That is rectified > in another separate series; > https://patchew.org/QEMU/[email protected]/ - The > only difference this patch series would make to this series is the > version numbers chosen in the 20th patch, which can be trivially updated > later depending on merge order.
I intend to submit a pull request for this series tomorrow, barring any complaints. Most of the feedback has been largely details, with no major pushback to the general strategy and content of the series, so I will instead vow to fix any lingering problems or feedback in follow-ups given that VM tests and GitLab CI see no regressions; I believe due diligence has been done. I apologize if this seems hasty...! Next steps for the Python Agenda are: - Fix rust nightly test (Patch v2 posted) - Drop avocado from qemu.git to fix python-check-tox (Series posted) - Drop debian 11 from GitLab CI tests (Series posted) - Collect any lingering fixes for qemu.qmp standalone repository, modernize to 3.9+, and publish v0.0.6 - Bump qemu.qmp in qemu.git to v0.0.6 - Bump minimum Python version to 3.12* and Sphinx to 7.x in June, when Debian 12 support is dropped. - Perform a "flag day" of autoformatting and cleaning up our Python code using modern type hint syntax and removing compatibility goop; introduce the use of the 'black' autoformatter for Python code - Finally Implement "make check-python" as a first-class, supported test. - Drop iotest 293 in favor of "make check-python". * Assuming FreeBSD upgrades to at least Python 3.12+ by then, otherwise, Python 3.11. Thanks, --js
