From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Cleber Rosa" <crosa@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Akihiko Odaki <akihiko.odaki@daynix.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Avocado 88.1 vs Python 3.12
Date: Tue, 9 Jul 2024 16:45:30 -0700 [thread overview]
Message-ID: <5aa7be9d-1ce1-4448-97c4-fb0d5c4c0985@linaro.org> (raw)
In-Reply-To: <56ef21cc-f2e3-42df-a114-b7368c77253b@linaro.org>
On 7/9/24 09:26, Philippe Mathieu-Daudé wrote:
> On 9/7/24 17:41, Richard Henderson wrote:
>> Hi guys,
>>
>> I have reinstalled my development box to ubuntu 24 (because the Rust support is better
>> than my previous install; ho hum). I thought I had tested everything in a VM before
>> committing, but I missed out on Avocado:
>>
>>> AVOCADO Downloading avocado tests VM image for aarch64
>>> Failed to load plugin from module "avocado.plugins.list": ModuleNotFoundError("No
>>> module named 'imp'") :
>
>
>> If I understand things correctly, the python "imp" package was deprecated, and has been
>> removed before v3.12. This is fixed in upstream avocado as of v93. But we have a hard
>> stop in pythondeps.toml at v92.
>>
>> Remind me what the blocker is to upgrading?
>
> IIRC we're waiting for v2 of:
> https://lore.kernel.org/qemu-devel/20231208190911.102879-1-crosa@redhat.com/
>
>
Yes indeed. There are two minor conflicts in rebasing this branch, but otherwise it
works. Cleber, do you have time to pick this up again?
r~
next prev parent reply other threads:[~2024-07-09 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 15:41 Avocado 88.1 vs Python 3.12 Richard Henderson
2024-07-09 16:26 ` Philippe Mathieu-Daudé
2024-07-09 23:45 ` Richard Henderson [this message]
2024-07-11 12:01 ` Thomas Huth
2024-07-11 12:30 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5aa7be9d-1ce1-4448-97c4-fb0d5c4c0985@linaro.org \
--to=richard.henderson@linaro.org \
--cc=akihiko.odaki@daynix.com \
--cc=crosa@redhat.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).