Hi Paul (2024.07.12_10:59:43_+0000) > > > The weird thing is that I can run "python3 -m build", even with the > > > options that pybuild introduces, outside the gbp buildpackage environment, > > > and it seems that the package data is obtained using setuptools_scm. But > > > as part of the gbp invocation, the package data is limited to that > > > mentioned in the deficient pyproject.toml file. > > > > Is your packaging in git? It'll be finding the list of files tracked by > > git, from git. > > The packaging is in git, yes. I suppose what I don't understand is the role > of > setuptools_scm in building a package for installation (or the construction of > a binary package).
It has 2 roles, both are optional the package may use them or not: 1. Determine the version from VCS tags 2. Determine the list of files that should be shipped in the package. > A source package will aim to incorporate all of the tracked files, but > a built/binary package may not. Yeah, roughly. Binary packages get "data" files included. These are typically non-Python files inside a Python module. Source packages get other sources, too. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
