Arch Linux User Repository

@amish: Thanks for checking!

@Morbius: Yes it worked now.

@amish: Found the issue. My existing shell environment modfied PYTHONPATH, affecting unit tests. Fixed in build 1.9.1-2.

@Morbius: Python 3.13.1

Remove python-fangfrisch first and then try building.

@amish: According to my own build logs, all 82 tests pass (14 tests skipped, as expected). I will set up a fresh Arch machine and retry. In the meantime, what Python version is running on your machine?

@Morbius: Checks failing again with this release.

The system where I am building this DOES NOT have python-fangfrish installed.

So tests are failing as follows:

test_config (unittest.loader._FailedTest.test_config) ... ERROR
test_db (unittest.loader._FailedTest.test_db) ... ERROR
test_download (unittest.loader._FailedTest.test_download) ... ERROR
test_dump (unittest.loader._FailedTest.test_dump) ... ERROR
test_log (unittest.loader._FailedTest.test_log) ... ERROR
test_refresh (unittest.loader._FailedTest.test_refresh) ... ERROR
test_task (unittest.loader._FailedTest.test_task) ... ERROR
test_util (unittest.loader._FailedTest.test_util) ... ERROR

======================================================================
ERROR: test_config (unittest.loader._FailedTest.test_config)
----------------------------------------------------------------------
ImportError: Failed to import test module: test_config
Traceback (most recent call last):
  File "/usr/lib/python3.13/unittest/loader.py", line 396, in _find_test_path
    module = self._get_module_from_name(name)
  File "/usr/lib/python3.13/unittest/loader.py", line 339, in _get_module_from_name
    __import__(name)
    ~~~~~~~~~~^^^^^^
  File "/home/foo/AUR/python-fangfrisch/src/fangfrisch-1.9.1/tests/test_config.py", line 22, in <module>
    from fangfrisch.config import LOG_METHOD_CONSOLE
ModuleNotFoundError: No module named 'fangfrisch'

So on for other tests.

If I first install old version (1.9.0) of python-fangfrisch then tests succeed.

So something is wrong somewhere.

Please check.

@amish: Yeah, that was a weird situation. Before unpacking the source tarball, the working directory should be empty, and only the Python interpreter itself should ever create "pycache" directories anywhere in the tree. Something strange happened there on your machine.

@Morbius - it worked. But I dont see any pycache directory in ~/.cache and issue never occurred earlier. Thanks.

@amish: I just built the previous Git master 2b40fd2c7b02a4d3edf6ef9f2b5d402efdd24f4a and did not encounter any problems. I suspect that the pycache directory on your machine, which caused sed to fail, was the remnant of some previous run. In the check() function, sed runs before "python -m unittest ...", and only the latter step is expected to create any pycache directories. However, I have added a small change to increase robustness.