From: Julien Stephan <jstephan@baylibre.com>
To: openembedded-core@lists.openembedded.org
Cc: Julien Stephan <jstephan@baylibre.com>
Subject: [PATCH v3 0/4] devtool/recipetool: add support of PEP-517
Date: Tue, 24 Oct 2023 16:40:17 +0200 [thread overview]
Message-ID: <20231024144022.1532605-1-jstephan@baylibre.com> (raw)
Hello all,
This series adds basic support for PEP-517 in recipetool/devtool, plus somes
others fixes.
Recipetool/devtool selftest passed locally
Missing features:
- extra or optionnal dependencies are not handled
- version number for dependencies are not handled (issue already present
for the legacy setuptool)
- 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.
Changes from v2:
- try to use tomllib from python core (since 3.11) and if not available,
try to import tomli (instead of toml, as tomllib and tomli have both the
same api)
- improve support for poetry: poetry looks for metadata into the
"tools.poetry" section instead of the "project" section
- add the selftests for the 3 supported backends. Skip the tests if
tomliib (python > 3.11) or tomli is not installed
- fix self test failing with the new "python3-" prefix added to
recipetool for python recipes
Julien Stephan (4):
scripts:recipetool:create_buildsys_python: prefix created recipes with
python3-
scripts:recipetool:create_buildsys_python: refactor code for futur
PEP517 addition
scripts:recipetool:create_buildsys_python: add PEP517 support
oeqa/selftest/recipetool: add selftest for PEP-517 recipe creation
meta/lib/oeqa/selftest/cases/recipetool.py | 106 +-
.../lib/recipetool/create_buildsys_python.py | 1017 +++++++++++------
2 files changed, 759 insertions(+), 364 deletions(-)
--
2.42.0
next reply other threads:[~2023-10-24 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 14:40 Julien Stephan [this message]
2023-10-24 14:40 ` [PATCH v3 1/4] scripts:recipetool:create_buildsys_python: prefix created recipes with python3- Julien Stephan
2023-10-24 14:40 ` [PATCH v3 2/4] scripts:recipetool:create_buildsys_python: refactor code for futur PEP517 addition Julien Stephan
2023-10-24 14:40 ` [PATCH v3 3/4] scripts:recipetool:create_buildsys_python: add PEP517 support Julien Stephan
2023-10-24 14:40 ` [PATCH v3 4/4] oeqa/selftest/recipetool: add selftest for PEP-517 recipe creation Julien Stephan
2023-10-25 14:11 ` [OE-core] [PATCH v3 0/4] devtool/recipetool: add support of PEP-517 Richard Purdie
2023-10-25 15:48 ` Julien Stephan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231024144022.1532605-1-jstephan@baylibre.com \
--to=jstephan@baylibre.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox