Closed kloczek closed 8 months ago
The test failed because you have the pkg
package installed:
pkg 0.0.0
Where this package comes from?
I'm closing this as the issue appears to be an unexpected pkg
package in the environment. I quickly scanned through the test fixtures and I don't think they're responsible for creating the pkg
package. Next step is to investigate why that's happening and possibly prevent it from happening. Feel free to comment if there's something this project could potentially do differently.
Trying to retest that found that in case of create some directory in project tree (in this case created by rpm) before start build it fails because because some bits are missing in pyproject.toml
+ /usr/bin/python3 -sBm build -w --no-isolation
* Getting build dependencies for wheel...
error: Multiple top-level packages discovered in a flat-layout: ['SPECPARTS', 'importlib_metadata'].
To avoid accidental inclusion of unwanted files or directories,
setuptools will not proceed with this build.
If you are trying to create a single distribution with multiple packages
on purpose, you should not rely on automatic discovery.
Instead, consider the following options:
1. set up custom discovery (`find` directive with `include` or `exclude`)
2. use a `src-layout`
3. explicitly set `py_modules` or `packages` with a list of names
To find more information, look for "package discovery" on setuptools docs.
ERROR Backend subprocess exited when trying to invoke get_requires_for_build_wheel
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulescut off from access to the public network
(pytest is executed with-m "not network"
)Here is pytest output:
Here is list of installed modules in build env