Closed kloczek closed 1 year ago
This is simply about IPython not being installed in your env.
One sec .. let me check 😋
Indeed it was missing ipyhon. Thank you very much 👍 😄
+ PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-executing-1.2.0-5.fc35.x86_64/usr/lib64/python3.8/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-executing-1.2.0-5.fc35.x86_64/usr/lib/python3.8/site-packages
+ /usr/bin/pytest -ra -m 'not network'
==================================================================================== test session starts ====================================================================================
platform linux -- Python 3.8.18, pytest-7.4.3, pluggy-1.3.0
rootdir: /home/tkloczko/rpmbuild/BUILD/executing-1.2.0
collected 59 items
tests/test_main.py ................................sssssssssssssss. [ 81%]
tests/test_pytest.py ........... [100%]
================================================================================== short test summary info ==================================================================================
SKIPPED [14] tests/test_main.py:680: These tests are very slow, enable them explicitly
SKIPPED [1] tests/test_main.py:696: These tests are very slow, enable them explicitly
============================================================================== 44 passed, 15 skipped in 13.04s ==============================================================================
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