Closed kloczek closed 1 year ago
Hmm, interesting. It's a new test for the old behaviour. I'll look into this tomorrow and let you know if I can repro and fix it. Thank you!
I believe it's fixed in v.0.28.1.
Just tested new version and all looks good 😄
+ /usr/bin/pytest -ra -m 'not network'
============================= test session starts ==============================
platform linux -- Python 3.8.16, pytest-7.2.1, pluggy-1.0.0
rootdir: /home/tkloczko/rpmbuild/BUILD/argh-0.28.1
collected 102 items
tests/test_assembling.py ................... [ 18%]
tests/test_completion.py ... [ 21%]
tests/test_decorators.py ...... [ 27%]
tests/test_dispatching.py ... [ 30%]
tests/test_integration.py .......xxx.................................... [ 75%]
..... [ 80%]
tests/test_interaction.py ..... [ 85%]
tests/test_regressions.py ....... [ 92%]
tests/test_utils.py ........ [100%]
=========================== short test summary info ============================
XFAIL tests/test_integration.py::test_simple_function_multiple
XFAIL tests/test_integration.py::test_simple_function_nested
XFAIL tests/test_integration.py::test_class_method_as_command
======================== 99 passed, 3 xfailed in 0.42s =========================
Thank you 👍
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