Running the test suite should work, if all dependencies are already installed, without accessing the network.
As described in a comment on issue 84 (thank you @attila-lendvai ), currently the test runner (make test) actively attempts to install dependencies from the package index, and other network access.
make test
Re-work the build system so that the test suite runner will succeed, if its package dependencies are satisfied already, in the absence of any network access.
I have a branch that intends to migrate all of the project specification, including build configuration, to PEP 621 'pyproject.toml' specification. Please see the work-in-progress branch wip/maintenance/pyproject.
@attila-lendvai, can you please try the code from that branch and see whether, with all the test dependencies installed (use python3 -m pip install .[test]), it behaves correctly by using python3 -m unittest discover?
python3 -m pip install .[test]
python3 -m unittest discover
With the migration to 'changelog-chug' for interrogating the Change Log at build time, merged to the 'main' branch, this issue is now resolved.
Metadata Update from @bignose: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)