Closed kloczek closed 1 year ago
::project
is what pytest-checkdocs
generates. I'm transferring the issue there.
Similar to jaraco.packaging
, pytest-checkdocs
uses build.util.project_wheel_metadata to load metadata for the wheel. https://github.com/pypa/build/issues/556 tracks the limitation that it's not possible to load wheel metadata without building an environment requiring network access. Now it's clear why https://github.com/jaraco/jaraco.packaging/pull/11 was a bad idea. It fixed the issue at the wrong level of abstraction, leaving pytest-checkdocs broken while fixing only jaraco.packaging.
This issue isn't going to be solved here - it needs to be solved in build.
Just retested 3.3.1 and pytest still fails
Please follow pypa/build#556 that attempts to capture the root of the issue.
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