mesonbuild / mesonbuild/meson-python

Document meson-python requirements on how `import('python').find_installation()` is called

Open
#233 5 comments 2 reactions 0 assignees View on GitHub
documentation
Dominant language
Python
Stars
180
Forks
93
Avg merge
2d 7h
Merged PRs (30d)
18

Description

meson-python invokes meson and meson may be run by a different Python interpreter than the one used to run meson-python via pip or build or other pep517 frontend. meson-python uses a native file to pass the python interpreter to build for to meson. AFAIK, this works only if a path to a Python interpreter is not explicitly passed as an argument to `import('python').find_installation()`. This should be documented.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the project documentation that explains meson-python's native file and its use of Meson's import('python').find_installation() entry point. Document the requirement about not passing an explicit Python interpreter path, and consider the work done when users can understand which interpreter meson-python passes to Meson and the limitation involved.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.