[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC 0/6] Switch iotests to pyvenv
|
From: |
Paolo Bonzini |
|
Subject: |
Re: [PATCH RFC 0/6] Switch iotests to pyvenv |
|
Date: |
Thu, 22 Jun 2023 23:04:57 +0200 |
On Thu, Jun 22, 2023 at 11:03 PM John Snow <jsnow@redhat.com> wrote:
> If we always install it in editable mode, and the path where it is
> "installed" is what we expect it to be, it shouldn't have any problems
> with being out of date.... I think. We could conceivably use the
> "faux" package version the internal package has to signal when the
> script needs to re-install it.
Stupid question, why not treat it just like avocado?
- [PATCH RFC 0/6] Switch iotests to pyvenv, John Snow, 2023/06/20
- [PATCH RFC 2/6] build, tests: Add qemu in-tree packages to pyvenv at configure time., John Snow, 2023/06/20
- [PATCH RFC 4/6] iotests: use the correct python to run linters, John Snow, 2023/06/20
- [PATCH RFC 6/6] iotests: don't add qemu.git/python to PYTHONPATH, John Snow, 2023/06/20
- [PATCH RFC 5/6] iotests: use pyvenv/bin/python3 to launch child test processes, John Snow, 2023/06/20
- [PATCH RFC 3/6] iotests: get rid of '..' in path environment output, John Snow, 2023/06/20
- [PATCH RFC 1/6] experiment: add mkvenv install, John Snow, 2023/06/20
- Re: [PATCH RFC 0/6] Switch iotests to pyvenv, Paolo Bonzini, 2023/06/21
- Re: [PATCH RFC 0/6] Switch iotests to pyvenv, Paolo Bonzini, 2023/06/22
- Re: [PATCH RFC 0/6] Switch iotests to pyvenv, John Snow, 2023/06/22
- Re: [PATCH RFC 0/6] Switch iotests to pyvenv,
Paolo Bonzini <=
- Re: [PATCH RFC 0/6] Switch iotests to pyvenv, John Snow, 2023/06/22
- Re: [PATCH RFC 0/6] Switch iotests to pyvenv, Paolo Bonzini, 2023/06/22
- Re: [PATCH RFC 0/6] Switch iotests to pyvenv, John Snow, 2023/06/22
- Re: [PATCH RFC 0/6] Switch iotests to pyvenv, Paolo Bonzini, 2023/06/22