diff options
| author | Julien Stephan <jstephan@baylibre.com> | 2023-10-25 17:46:58 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-10-27 08:28:38 +0100 |
| commit | d4debbf5b7ff9e0f489530aa748c559d631eeb57 (patch) | |
| tree | 964a40422cebd4ac5ca84f1c37fdad96c04af5da /scripts/contrib/patchreview.py | |
| parent | e64e92f2de4b182d087d7d88326aa7d06f59776e (diff) | |
| download | poky-d4debbf5b7ff9e0f489530aa748c559d631eeb57.tar.gz | |
recipetool/create_buildsys_python: add PEP517 support
Add basic support for PEP517 [1] for the 3 following backends that are
supported by bitbake:
- setuptools.build_meta
- poetry.core.masonry.api
- flit_core.buildapi
If a pyproject.toml file is found, use it to create the recipe,
otherwise fallback to the old setup.py method.
Some projects can declare a minimal pyproject.toml file, and put all
the metadata in setup.py/setup.cfg/requirements.txt .. theses cases
are not handled. If a pyproject.toml file is found, assumes it has all
necessary metadata.
As for the old setup.py method, version numbers for dependencies are not
handled.
Some features may be missing, such as the extra dependencies.
[YOCTO #14737]
[1]: https://peps.python.org/pep-0517/
(From OE-Core rev: c7d8d15b2d0a9ecd210bd247fa0df31d9f458873)
Signed-off-by: Julien Stephan <jstephan@baylibre.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/contrib/patchreview.py')
0 files changed, 0 insertions, 0 deletions