14737 2022-02-22 23:03:39 +0000 recipetool/devtool: add support for Python PEP-517 (pyproject.toml and setup.cfg) packages 2025-02-14 16:48:19 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 4.0 x86 Multiple RESOLVED FIXED Medium+ normal 5.0 M2 1 tim.orling ross.burton jstephan meta.mr.watcher meta.watcher randy.macleod ross.burton sgw tvgamblin --- --- Yes (doc changes required) oldest_to_newest 92632 0 tim.orling 2022-02-22 23:03:39 +0000 The current recipetool code only understands 'distutils' and legacy 'setuptools' (setup.py) invocations. We need to check for presence of pyproject.toml and then _if_ it supports proper PEP-517 backend, make a stab at DEPENDS and RDEPENDS. While we are at it, we should probably remove 'distutils' support completely? 92658 1 randy.macleod 2022-02-24 15:44:26 +0000 Backport to 3.5 if not too invasive. 92665 2 tim.orling 2022-02-24 16:38:09 +0000 The first thing that must be changed is the logic at: https://git.yoctoproject.org/poky/tree/scripts/lib/recipetool/create_buildsys_python.py#n158 # Check for non-zero size setup.py files setupfiles = RecipeHandler.checkfiles(srctree, ['setup.py']) for fn in setupfiles: if os.path.getsize(fn): break else: return False This also needs to look for pyproject.toml and setup.cfg files. Based on what files are found, make a decision of how to proceed. For instance, if a pyproject.toml is present, has a [build-system] section and a build-backend that we know about (have a bbclass for) then the recipe should inherit e.g. flit_core, setuptools_build_meta or poetry_core (WIP). Looking for dependencies will also need more than one way to handle it, as recipes without setup.py might include such info in setup.cfg or in pyproject.toml. 97304 3 jstephan 2023-11-22 15:28:00 +0000 merged on https://git.yoctoproject.org/poky/commit/?id=d4debbf5b7ff9e0f489530aa748c559d631eeb57 so closing 97306 4 tim.orling 2023-11-22 16:45:10 +0000 ACCEPTED means you have accepted the bug and are working on it. The way to mark a bug as closed is RESOLVED FIXED. 97309 5 jstephan 2023-11-23 08:06:49 +0000 (In reply to Tim Orling from comment #4) > ACCEPTED means you have accepted the bug and are working on it. The way to > mark a bug as closed is RESOLVED FIXED. got it thank you! 100974 6 randy.macleod 2025-02-14 16:46:24 +0000 bulk change to add Saul's non-WR address. 101056 7 randy.macleod 2025-02-14 16:48:19 +0000 Bulk change: Remove Saul's old WR address.