On Wed, Feb 9, 2022, 8:35 AM Peter Maydell <peter.mayd...@linaro.org> wrote:
> On Mon, 7 Feb 2022 at 21:34, John Snow <js...@redhat.com> wrote: > > > > When invoking setup.py directly, the default behavior for 'install' is > > to run the bdist_egg installation hook, which is ... actually deprecated > > by setuptools. It doesn't seem to work quite right anymore. > > > > By contrast, 'pip install' will invoke the bdist_wheel hook > > instead. This leads to differences in behavior for the two approaches. I > > advocate using pip in the documentation in this directory, but the > > 'setup.py' which has been used for quite a long time in the Python world > > may deceptively appear to work at first glance. > > > > Add an error message that will save a bit of time and frustration > > that points the user towards using the supported installation > > invocation. > > While we're on the topic of python installation, is there any way > to suppress or otherwise deal with the warning Meson prints out? > > WARNING: Broken python installation detected. Python files installed > by Meson might not be found by python interpreter. > > (I vaguely recall tracking down a meson bug, and this seems to be > some issue the meson developers have with the way Ubuntu/Debian > have done their python packaging. But I forget the details.) > > thanks > -- PMM > Unknown, I don't think I see this message on Fedora. Are you seeing it from Debian? I'll see if it shows up in any of the VM build tests. >
