[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Building python extensions with meson



Ciao,

Enrico Zini <enrico@enricozini.org> (2022-12-17):
> The package builds fine on bullseye and bookworm, but fails to build
> on sid. On sid, meson tries to install the Python extension under
> /usr/local instead of /usr.
> 
> I do not understand what has changed, nor how to fix it.
[…]
> Did something break between bookworm and sid, in the interaction
> between meson and Python?

As far as I know, get_path()'s implemented in meson's python.py module
(not the python3.py one), and the code path is the same there (no if
branch taken, value returned via the last return statement); also, both
have the same install_env (prefix).

The main difference is that in testing:

    rel_path: lib/python3/dist-packages

while in unstable:

    rel_path: local/lib/python3.10/dist-packages

This comes from setuptools 65.5.0-1.1 (NMUer cc'd):

   * Install distutils-precedence.pth, to avoid packages need to hack import
     order in setup.py. Closes: #1025216

which is consistent with the aforementioned rel_path's being derived
from a specific item in a list:
  https://sources.debian.org/src/meson/0.64.1-1.1/mesonbuild/modules/python.py/#L452-L453

No idea how to best fix or work around this though. Good luck.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature


Reply to: