On 2/27/20 9:14 AM, Philippe Mathieu-Daudé wrote:
On 2/27/20 1:06 AM, John Snow wrote:
The right way to solve this is to come up with a virtual environment
infrastructure that sets all the paths correctly, and/or to create
installable python modules that can be imported normally.
That's hard, so just silence this error for now.
I'm tempted to NAck this and require an "installable python module"...
Let's discuss why it is that hard!
I've been tricked into this before. It's not work I am interested in
doing right now; it's WAY beyond the scope of what I am doing here.
It involves properly factoring all of our python code, deciding which
portions are meant to be installed separately from QEMU itself, coming
up with a versioning scheme, packaging code, and moving code around in
many places.
Then it involves coming up with tooling and infrastructure for creating
virtual environments, installing the right packages to it, and using it
to run our python tests.
No, that's way too invasive. I'm not doing it and I will scream loudly
if you make me.
A less invasive hack involves setting the python import path in a
consolidated spot so that python knows where it can import from. This
works, but might break the ability to run such tests as one-offs without
executing the environment setup.
Again, not work I care to do right now and so I won't. The benefit of
these patches is to provide some minimum viable CI CQA for Python where
we had none before, NOT fix every possible Python problem in one shot.