On Thu, Aug 10, 2023 at 1:52 PM Philippe Mathieu-Daudé
<[email protected]> wrote:
> Does this fix the second point of commit eaf245becd ("Revert
> "tests/requirements.txt: bump up avocado-framework version to 101.0"")
>
> > Second, the recent changes to Python handling mean that there is
> > a single virtual environment for all the build, instead of a separate
> > one for testing.
This was reverted and Avocado has a separate venv than pyvenv/ (which
is the one created by configure). This series makes it possible to
have again a single virtual environment for all the build.
> > Avocado is not logging of command lines or terminal output, and
> > not collecting Python logs outside the avocado namespace.
>
> This seems to be fixed in Avocado 102.0:
Correct.
> Assuming this is enough for macOS, what would be the next change,
> moving to 102.0 or integrate 102.0 in the current set? I.e.:
>
> avocado-framework = { accepted = "(>=88.1, <93.0, 102.0)", ... }
The plan is to:
1) wait for the next LTS release of Avocado (103.0)
2) wait for it to be packaged in Fedora
3) change "accepted" to be "~= 103.0"
Users of Fedora will have to switch from the 92.0 module to the 103.0
module if they want to use the system avocado.
Paolo
