2.5.6: pytest is failing

Continuations of the https://github.com/WoLpH/python-utils/issues/18
Just normal build, install and test cycle used on building package from non-root account:

"setup.py build"
"setup.py install --root </install/prefix>"
"pytest with PYTHONPATH pointing to setearch and sitelib inside </install/prefix>

+ PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-utils-2.5.6-2.fc35.x86_64/usr/lib64/python3.8/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-utils-2.5.6-2.fc35.x86_64/usr/lib/python3.8/site-packages
+ /usr/bin/pytest -ra
=========================================================================== test session starts ============================================================================
platform linux -- Python 3.8.11, pytest-6.2.4, py-1.10.0, pluggy-0.13.1
benchmark: 3.4.1 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.000005 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=100000)
rootdir: /home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6, configfile: pytest.ini
plugins: forked-1.3.0, shutil-1.7.0, virtualenv-1.7.0, expect-1.1.0, httpbin-1.0.0, flake8-1.0.7, timeout-1.4.2, betamax-0.8.1, freezegun-0.4.2, case-1.5.3, isort-1.3.0, aspectlib-1.5.2, asyncio-0.15.1, toolbox-0.5, aiohttp-0.3.0, checkdocs-2.7.0, mock-3.6.1, rerunfailures-9.1.1, requests-mock-1.9.3, cov-2.12.1, pyfakefs-4.5.0, flaky-3.7.0, benchmark-3.4.1, xdist-2.3.0, pylama-7.7.1, datadir-1.3.1, regressions-2.2.0, cases-3.6.3, hypothesis-6.14.4, Faker-8.10.3, xprocess-0.18.1, black-0.3.12
collected 35 items

. .                                                                                [  2%]
setup.py F                                                                                [  5%]
_python_utils_tests/__init__.py .                                                                                [  8%]
_python_utils_tests/test_import.py .......                                                                                [ 29%]
_python_utils_tests/test_python_utils.py ..                                                                                [ 35%]
python_utils/__init__.py .                                                                                [ 38%]
python_utils/__about__.py .                                                                                [ 41%]
python_utils/compat.py .                                                                                [ 44%]
python_utils/converters.py F......                                                                                [ 64%]
python_utils/decorators.py ..                                                                                [ 70%]
python_utils/formatters.py F..                                                                                [ 79%]
python_utils/import_.py .                                                                                [ 82%]
python_utils/logger.py F.                                                                                [ 88%]
python_utils/terminal.py F                                                                                [ 91%]
python_utils/time.py F..                                                                                [100%]

================================================================================= FAILURES =================================================================================
_______________________________________________________________________ FLAKE8-check(ignoring W391) ________________________________________________________________________
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/setup.py:3:1: H306: imports not in alphabetical order (sys, setuptools)

---------------------------------------------------------------------------- Captured log call -----------------------------------------------------------------------------
WARNING  flake8.options.manager:manager.py:186 option --indent-size: please update `help=` text to use %(default)s instead of %default -- this will be an error in the future
WARNING  flake8.options.manager:manager.py:207 option --max-complexity: please update from optparse string `type=` to argparse callable `type=` -- this will be an error in the future
_______________________________________________________________________ FLAKE8-check(ignoring W391) ________________________________________________________________________
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:1:40: H301: one import per line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:6:1: H306: imports not in alphabetical order (six, math)
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:10:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:10:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:11:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:11:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:12:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:12:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:13:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:13:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:14:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:14:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:15:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:15:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:16:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:16:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:17:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:17:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:18:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:18:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:19:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:19:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:20:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:20:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:21:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:21:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:22:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:22:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:23:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:23:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:24:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:24:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:25:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:25:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:26:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:26:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:27:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:27:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:28:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:28:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:29:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:29:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:30:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:30:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:31:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:31:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:32:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:32:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:33:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:33:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:34:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:34:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:35:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:35:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:36:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:36:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:37:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:37:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:38:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:38:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:39:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:39:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:40:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:40:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:41:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:41:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:42:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:42:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:43:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:43:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:44:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:44:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:45:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:45:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:46:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:46:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:47:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:47:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:48:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:48:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:49:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:49:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:50:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:50:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:51:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:51:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:52:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:52:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:53:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:53:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:54:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:54:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:55:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:55:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:56:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:56:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:57:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:57:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:58:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:58:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:59:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:59:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:60:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:60:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:61:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:61:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:62:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:62:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:63:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:63:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:64:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:64:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:65:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:65:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:66:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:66:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:89:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:89:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:90:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:90:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:91:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:91:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:92:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:92:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:93:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:93:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:94:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:94:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:95:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:95:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:96:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:96:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:97:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:97:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:98:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:98:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:99:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:99:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:100:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:100:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:101:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:101:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:102:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:102:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:103:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:103:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:104:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:104:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:105:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:105:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:106:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:106:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:107:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:107:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:108:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:108:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:109:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:109:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:110:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:110:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:111:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:111:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:112:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:112:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:113:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:113:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:114:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:114:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:115:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:115:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:116:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:116:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:117:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:117:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:118:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:118:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:119:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:119:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:120:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:120:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:121:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:121:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:122:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:122:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:123:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:123:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:124:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:124:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:125:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:125:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:126:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:126:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:127:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:127:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:128:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:128:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:129:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:129:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:130:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:130:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:131:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:131:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:132:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:132:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:133:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:133:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:134:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:134:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:135:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:135:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:136:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:136:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:137:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:137:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:138:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:138:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:139:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:139:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:161:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:162:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:163:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:164:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:165:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:166:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:167:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:168:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:169:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:170:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:171:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:172:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:173:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:174:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:175:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:176:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:177:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:239:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:239:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:240:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:240:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:241:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:241:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:242:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:242:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:243:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:243:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:244:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:244:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:245:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:245:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:246:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:246:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:247:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:247:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:248:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:248:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:249:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:249:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:250:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:250:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:251:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:251:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:252:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:252:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:253:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:253:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:254:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:254:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:255:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:255:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:256:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:256:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:257:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:257:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:258:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:258:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:259:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:259:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:260:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:260:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:261:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:261:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:262:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:262:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:263:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:263:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:264:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:264:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:265:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:265:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:266:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:266:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:267:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:267:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:268:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:268:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:269:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:269:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:270:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:270:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:271:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:271:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:272:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:272:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:273:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:273:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:274:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:274:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:275:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:275:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:276:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:276:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:277:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:277:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:278:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:278:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:279:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:279:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:280:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:280:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:281:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:281:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:282:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:282:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:283:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:283:1: H405: multi line docstring summary not separated with an empty line

---------------------------------------------------------------------------- Captured log call -----------------------------------------------------------------------------
WARNING  flake8.options.manager:manager.py:186 option --indent-size: please update `help=` text to use %(default)s instead of %default -- this will be an error in the future
WARNING  flake8.options.manager:manager.py:207 option --max-complexity: please update from optparse string `type=` to argparse callable `type=` -- this will be an error in the future
_______________________________________________________________________ FLAKE8-check(ignoring W391) ________________________________________________________________________
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:43:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:43:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:44:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:44:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:45:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:45:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:46:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:46:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:47:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:47:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:48:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:48:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:49:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:49:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:50:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:50:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:51:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:51:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:52:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:52:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:53:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:53:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:54:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:54:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:55:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:55:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:56:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:56:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:57:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:57:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:58:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:58:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:59:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:59:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:60:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:60:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:61:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:61:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:62:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:62:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:63:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:63:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:64:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:64:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:65:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:65:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:66:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:66:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:67:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:67:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:68:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:68:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:69:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:69:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:70:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:70:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:71:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:71:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:72:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:72:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:73:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:73:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:74:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:74:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:75:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:75:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:76:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:76:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:77:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:77:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:78:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:78:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:79:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:79:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:80:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:80:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:81:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:81:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:82:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:82:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:83:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:83:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:84:1: H404: multi line docstring should start without a leading new line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:84:1: H405: multi line docstring summary not separated with an empty line

---------------------------------------------------------------------------- Captured log call -----------------------------------------------------------------------------
WARNING  flake8.options.manager:manager.py:186 option --indent-size: please update `help=` text to use %(default)s instead of %default -- this will be an error in the future
WARNING  flake8.options.manager:manager.py:207 option --max-complexity: please update from optparse string `type=` to argparse callable `type=` -- this will be an error in the future
_______________________________________________________________________ FLAKE8-check(ignoring W391) ________________________________________________________________________
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:2:1: H306: imports not in alphabetical order (logging, functools)
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:8:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:9:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:10:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:11:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:12:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:13:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:14:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:15:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:16:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:17:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:18:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:19:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:20:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:21:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:22:1: H405: multi line docstring summary not separated with an empty line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/logger.py:23:1: H405: multi line docstring summary not separated with an empty line

---------------------------------------------------------------------------- Captured log call -----------------------------------------------------------------------------
WARNING  flake8.options.manager:manager.py:186 option --indent-size: please update `help=` text to use %(default)s instead of %default -- this will be an error in the future
WARNING  flake8.options.manager:manager.py:207 option --max-complexity: please update from optparse string `type=` to argparse callable `type=` -- this will be an error in the future
_______________________________________________________________________ FLAKE8-check(ignoring W391) ________________________________________________________________________
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/terminal.py:84:34: H301: one import per line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/terminal.py:131:13: H306: imports not in alphabetical order (termios, struct)

---------------------------------------------------------------------------- Captured log call -----------------------------------------------------------------------------
WARNING  flake8.options.manager:manager.py:186 option --indent-size: please update `help=` text to use %(default)s instead of %default -- this will be an error in the future
WARNING  flake8.options.manager:manager.py:207 option --max-complexity: please update from optparse string `type=` to argparse callable `type=` -- this will be an error in the future
_______________________________________________________________________ FLAKE8-check(ignoring W391) ________________________________________________________________________
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/time.py:2:1: H306: imports not in alphabetical order (six, datetime)

---------------------------------------------------------------------------- Captured log call -----------------------------------------------------------------------------
WARNING  flake8.options.manager:manager.py:186 option --indent-size: please update `help=` text to use %(default)s instead of %default -- this will be an error in the future
WARNING  flake8.options.manager:manager.py:207 option --max-complexity: please update from optparse string `type=` to argparse callable `type=` -- this will be an error in the future

---------- coverage: platform linux, python 3.8.11-final-0 -----------
Name                         Stmts   Miss Branch BrPart  Cover   Missing
------------------------------------------------------------------------
python_utils/__about__.py        6      0      0      0   100%
python_utils/__init__.py         0      0      0      0   100%
python_utils/compat.py           0      0      0      0   100%
python_utils/converters.py      69      0     38      0   100%
python_utils/decorators.py       6      0      2      0   100%
python_utils/formatters.py      29      0     20      0   100%
python_utils/import_.py         32      0     20      0   100%
python_utils/logger.py          34      0      2      0   100%
python_utils/terminal.py         1      0      0      0   100%
python_utils/time.py            25      0      8      0   100%
------------------------------------------------------------------------
TOTAL                          202      0     90      0   100%
Coverage HTML written to dir htmlcov

Required test coverage of 100.0% reached. Total coverage: 100.00%
========================================================================= short test summary info ==========================================================================
FAILED setup.py::FLAKE8
FAILED python_utils/converters.py::FLAKE8
FAILED python_utils/formatters.py::FLAKE8
FAILED python_utils/logger.py::FLAKE8
FAILED python_utils/terminal.py::FLAKE8
FAILED python_utils/time.py::FLAKE8
====================================================================== 6 failed, 28 passed in 11.34s =======================================================================
pytest-xprocess reminder::Be sure to terminate the started process by running 'pytest --xkill' if you have not explicitly done so in your fixture with 'xprocess.getinfo(<process_name>).terminate()'.

[tkloczko@barrel SPECS]$ pip show pytest-flake8
Name: pytest-flake8
Version: 1.0.7
Summary: pytest plugin to check FLAKE8 requirements
Home-page: https://github.com/tholo/pytest-flake8
Author: Thorsten Lockert
Author-email<EMAIL_ADDRESS>License: BSD License
Location: /usr/lib/python3.8/site-packages
Requires: flake8, pytest
Required-by:

I think something might be mutilating the files somehow, because as far as I am aware, the code is fully H405 compliant and I cannot reproduce that error at all.
It could be related to testing from the installed directory instead of the source directory, I would recommend running tests before building, followed by building and installing.

Actually... I wonder where did you get that version of flake8? The current release is at 3.9.2 and I can't even find 1.0.7 in the list of releases: https://pypi.org/project/flake8/#history
Going by surrounding version numbers however, that version is 10 years old

Hmm .. so it may implies that one of the pytaest extensions may have some bug (?)
FYI. Just to give you some context. I'm packaging python modules as rpm packages and at ht emoment I have +550 packages anongst +450 is tested using pytest and exacly the same build/install/testing methodology.
Only python-utils I see pytest errors like above.
I'm not suggesting anything and to be honest I;m not fully aware what cold be wrong with H405 compliandce.
If testing not source tree but waht actually is installed is causing that effect that may mean that install is messing something in those files.
Nevertheless "/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/formatters.py:84:1" it is in source tree.
Here what I see in that comment:
     41
     42 def timesince(dt, default='just now'):
     43     '''
     44     Returns string representing 'time since' e.g.
     45     3 days ago, 5 hours ago etc.
     46
     47     >>> now = datetime.datetime.now()
     48     >>> timesince(now)
     49     'just now'
     50     >>> timesince(now - datetime.timedelta(seconds=1))
     51     '1 second ago'
     52     >>> timesince(now - datetime.timedelta(seconds=2))
     53     '2 seconds ago'
     54     >>> timesince(now - datetime.timedelta(seconds=60))
     55     '1 minute ago'
     56     >>> timesince(now - datetime.timedelta(seconds=61))
     57     '1 minute and 1 second ago'
     58     >>> timesince(now - datetime.timedelta(seconds=62))
     59     '1 minute and 2 seconds ago'
     60     >>> timesince(now - datetime.timedelta(seconds=120))
     61     '2 minutes ago'
     62     >>> timesince(now - datetime.timedelta(seconds=121))
     63     '2 minutes and 1 second ago'
     64     >>> timesince(now - datetime.timedelta(seconds=122))
     65     '2 minutes and 2 seconds ago'
     66     >>> timesince(now - datetime.timedelta(seconds=3599))
     67     '59 minutes and 59 seconds ago'
     68     >>> timesince(now - datetime.timedelta(seconds=3600))
     69     '1 hour ago'
     70     >>> timesince(now - datetime.timedelta(seconds=3601))
     71     '1 hour and 1 second ago'
     72     >>> timesince(now - datetime.timedelta(seconds=3602))
     73     '1 hour and 2 seconds ago'
     74     >>> timesince(now - datetime.timedelta(seconds=3660))
     75     '1 hour and 1 minute ago'
     76     >>> timesince(now - datetime.timedelta(seconds=3661))
     77     '1 hour and 1 minute ago'
     78     >>> timesince(now - datetime.timedelta(seconds=3720))
     79     '1 hour and 2 minutes ago'
     80     >>> timesince(now - datetime.timedelta(seconds=3721))
     81     '1 hour and 2 minutes ago'
     82     >>> timesince(datetime.timedelta(seconds=3721))
     83     '1 hour and 2 minutes ago'
     84     '''

I've been testing on several systems, bare, in dockers and using tox and I can't find a single method to reproduce the issue...
That file looks good to me.
What's weirder... I can't find this message in the source of pycodestyle, flake8 or any other repository. And it looks like something that should originate from pycodestyle.
Specifically I looked for both H405 and "multi line docstring summary not separated with an empty line"
I can't find anything codebase yet that could result in that error.

Either the docstrings need to be fixed as they really aren't supposed to begin with a newline character and remove any empty lines that are immediately after a docstring
you can also edit the pytest.ini file and add the H404 and H405 errors to the ignore statement for flake8.
flake8-ignore =
    *.py W391,H404,H405

this is wrong
def get_terminal_size():  # pragma: no cover
    '''Get the current size of your terminal

    Multiple returns are not always a good idea, but in this case it greatly
    simplifies the code so I believe it's justified. It's not the prettiest
    function but that's never really possible with cross-platform code.

    Returns:
        width, height: Two integers containing width and height
    '''

    try:
        # Default to 79 characters for IPython notebooks
        from IPython import get_ipython

Empty line after docstring
def format_time(timestamp, precision=datetime.timedelta(seconds=1)):
    '''Formats timedelta/datetime/seconds

    >>> format_time('1')
    '0:00:01'
    >>> format_time(1.234)
    '0:00:01'
    >>> format_time(1)
    '0:00:01'
    >>> format_time(datetime.datetime(2000, 1, 2, 3, 4, 5, 6))
    '2000-01-02 03:04:05'
    >>> format_time(datetime.date(2000, 1, 2))
    '2000-01-02'
    >>> format_time(datetime.timedelta(seconds=3661))
    '1:01:01'
    >>> format_time(None)
    '--:--:--'
    >>> format_time(format_time)  # doctest: +ELLIPSIS
    Traceback (most recent call last):
        ...
    TypeError: Unknown type ...

    '''
    precision_seconds = precision.total_seconds()

Empty line at end of docstring
def to_int(input_, default=0, exception=(ValueError, TypeError), regexp=None):
    r'''
    Convert the given input to an integer or return default

    When trying to convert the exceptions given in the exception parameter
    are automatically catched and the default will be returned.
    The regexp parameter allows for a regular expression to find the digits
    in a string.

    When True it will automatically match any digit in the string.
    When a (regexp) object (has a search method) is given, that will be used.
    WHen a string is given, re.compile will be run over it first

    The last group of the regexp will be used as value

    >>> to_int('abc')
    0
    >>> to_int('1')
    1
    >>> to_int('abc123')
    0
    >>> to_int('123abc')
    0
    >>> to_int('abc123', regexp=True)
    123
    >>> to_int('123abc', regexp=True)
    123
    >>> to_int('abc123abc', regexp=True)
    123
    >>> to_int('abc123abc456', regexp=True)
    123
    >>> to_int('abc123', regexp=re.compile(r'(\d+)'))
    123
    >>> to_int('123abc', regexp=re.compile(r'(\d+)'))
    123
    >>> to_int('abc123abc', regexp=re.compile(r'(\d+)'))
    123
    >>> to_int('abc123abc456', regexp=re.compile(r'(\d+)'))
    123
    >>> to_int('abc123', regexp=r'(\d+)')
    123
    >>> to_int('123abc', regexp=r'(\d+)')
    123
    >>> to_int('abc', regexp=r'(\d+)')
    0
    >>> to_int('abc123abc', regexp=r'(\d+)')
    123
    >>> to_int('abc123abc456', regexp=r'(\d+)')
    123
    >>> to_int('1234', default=1)
    1234
    >>> to_int('abc', default=1)
    1
    >>> to_int('abc', regexp=123)
    Traceback (most recent call last):
    ...
    TypeError: unknown argument for regexp parameter: 123
    '''

    if regexp is True:
        regexp = re.compile(r'(\d+)')

Empty line as the first line in the docstring & empty line after the  docstring
this is correct
def camel_to_underscore(name):
    '''Convert camel case style naming to underscore style naming

    If there are existing underscores they will be collapsed with the
    to-be-added underscores. Multiple consecutive capital letters will not be
    split except for the last one.

    >>> camel_to_underscore('SpamEggsAndBacon')
    'spam_eggs_and_bacon'
    >>> camel_to_underscore('Spam_and_bacon')
    'spam_and_bacon'
    >>> camel_to_underscore('Spam_And_Bacon')
    'spam_and_bacon'
    >>> camel_to_underscore('__SpamAndBacon__')
    '__spam_and_bacon__'
    >>> camel_to_underscore('__SpamANDBacon__')
    '__spam_and_bacon__'
    '''
    output = []
    for i, c in enumerate(name):
        if i > 0:

If an empty line at the top of the  docstring is wanted (this is what i prefer for readability) you would do the following

def dummy_func():
    '''\
    Description

    Additional information

    Parameter information
    '''
    pass  # start code on this line

The above should pass the tests. If it does not then there is a bug in the testing program, it is probably not reading the actual docstring which is how it should determine if there is an empty line at the beginning of the docstring.
There are so many code style specs that simply do not make any sense. An example is a function definition should not look like this

def some_func(
        param1,
        param2,
        param3,
        param4,
        param5,
        param6,
        param7,
        param8,
        param9
):
    if this:
        pass
    else:
        pass

the reasoning is because the original author of Python doesn't like to see the frown face "):"..  Not far an actual reason that would make any sense. Readability gets sacrificed because of a personal feeling of seeing a frown emoticon.
so instead it  should look like this

def some_func(param1, param2, param3,
        param4, param5, param6,
        param7, param8, param9):
    if this:
        pass
    else:
        pass

I think the first example is by far easier to read. which brings us  to this example which is OK to do because the closing ")" doesn't look like the frown emoticon.
some_tuple = (
    1,
    2,
    3,
    4,
    5,
    6,
    7,
    8.
    9
)

now these 2 errors are ambiguous and make zero sense to have both of them shown
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:1:40: H301: one import per line
/home/tkloczko/rpmbuild/BUILD/python-utils-2.5.6/python_utils/converters.py:6:1: H306: imports not in alphabetical order (six, math)

why the second error if the first isn't allowed???

If an empty line at the top of the docstring is wanted (this is what i prefer for readability) you would do the following

I agree. These are warnings that I would like to disable.

I think the first example is by far easier to read. which brings us to this example which is OK to do because the closing ")" doesn't look like the frown emoticon.

I think it depends on the case. If there are many similar parameters than I would opt for having multiple arguments on a single line. If the parameters are mostly long and/or very different than it can be more readable to have a new one for every line.
In any case, some fixes need to be made.

yeah it's not a big deal, almost all of the docstrings are correct there are only a few that need to be cleaned up to be complaint with pytest. The import stuff needs to be disabled.  the order in which modules are imported shouldn't matter at all. The only pep that I agree with concerning the imports is not using from some_module import * as this makes it really difficult to know what has come from where, this can turn into an even larger snafu if you have more then a single import like that. I have to admit I am guilty of using from some_module import *  because of laziness LOL.
what it boils down to  is state here https://www.python.org/dev/peps/pep-0008/#toc-entry-2

A style guide is about consistency. Consistency with this style guide is important. Consistency within a project is more important. Consistency within one module or function is the most important.

However, know when to be inconsistent -- sometimes style guide recommendations just aren't applicable. When in doubt, use your best judgment.

The pep is not rules, it is a guide and as such makes the things contained within it suggestions. This is one of the reasons why I do not like using code style testing programs. I know that they are mainly around to lessen the workload of the maintainer(s)/author(s) of a repository. It is a double edged sword tho. Having a maintainer/author spend the time to look at the code is really important hing to do. having automated programs to do things leads to buggy code. Just because it works in a test doesn't mean it is bug free code. if an author/maintainer relies on style tests and unit tests and merges codes based on those passing and not actually looking at the code is not a good thing. I believe that more and more of this kind of thing is happening. I am seeing more often Python libraries that I have to monkey patch to make them functional.
The time spent by an author/maintainer to actually review   the code for things like style increases the probability that a bug will be seen before the code ever gets merged. It also gives the author/maintainer the opportunity to become familiar with that is being added instead of them having to figure it out at a later time if a bug in the code has shown it's self.

me personally I like to have a single newline after a docstring before the start of the code. a docstring is technically a variable
would you do this?
some_var1 = """
Convert camel case style naming to underscore style naming

    If there are existing underscores they will be collapsed with the
    to-be-added underscores. Multiple consecutive capital letters will not be
    split except for the last one.

    >>> camel_to_underscore('SpamEggsAndBacon')
    'spam_eggs_and_bacon'
    >>> camel_to_underscore('Spam_and_bacon')
    'spam_and_bacon'
    >>> camel_to_underscore('Spam_And_Bacon')
    'spam_and_bacon'
    >>> camel_to_underscore('__SpamAndBacon__')
    '__spam_and_bacon__'
    >>> camel_to_underscore('__SpamANDBacon__')
    '__spam_and_bacon__'
"""
if this:
    pass
else:
    pass

probably not because the if else code segment below gets lost. It is a lot easier read this way
some_var1 = """
Convert camel case style naming to underscore style naming

    If there are existing underscores they will be collapsed with the
    to-be-added underscores. Multiple consecutive capital letters will not be
    split except for the last one.

    >>> camel_to_underscore('SpamEggsAndBacon')
    'spam_eggs_and_bacon'
    >>> camel_to_underscore('Spam_and_bacon')
    'spam_and_bacon'
    >>> camel_to_underscore('Spam_And_Bacon')
    'spam_and_bacon'
    >>> camel_to_underscore('__SpamAndBacon__')
    '__spam_and_bacon__'
    >>> camel_to_underscore('__SpamANDBacon__')
    '__spam_and_bacon__'
"""

if this:
    pass
else:
    pass

it amazes me that docstrings get treated different then what they really are, a variable. using __doc__ = """some doc"""  is the same as """some_doc""".

point in fact. what you and I are doing with the unit_converter PR.
the original version of the PR did you have any clue how it worked??? I wrote it and sure as hell I didn't know how it worked!! LMAO. I stated right out of the gate that it was not to be merged and that "we" needed to work on it. I said we because ultimately you are the one that is going to have to maintain it so you need to know how it works. while I have been making most of the changes the changes I am making are to simplify it so it will be less of a headache should a bug show up or if you need to add something to it.

Just because it works in a test doesn't mean it is bug free code. if an author/maintainer relies on style tests and unit tests and merges codes based on those passing and not actually looking at the code is not a good thing. I believe that more and more of this kind of thing is happening. I am seeing more often Python libraries that I have to monkey patch to make them functional.

The automated testing and code style checking are mostly a hygiene factor to be honest. When the code style is consistent it is easier to spot errors in the code.
And it takes care of silly things such as missing imports, missing requirements, Python version incompatibility, etc...

The time spent by an author/maintainer to actually review the code for things like style increases the probability that a bug will be seen before the code ever gets merged. It also gives the author/maintainer the opportunity to become familiar with that is being added instead of them having to figure it out at a later time if a bug in the code has shown it's self.

That's definitely one way of looking at it, I'm coming from the other side of things. Every minute spent styling the code is a minute lost to checking the code. And I do want to get all issues resolved at some point :)

point in fact. what you and I are doing with the unit_converter PR. the original version of the PR did you have any clue how it worked??? I wrote it and sure as hell I didn't know how it worked!! LMAO.

Partially yes, but largely no. That's why I started writing a few tests to see if the code works and behaves as I expected from reading it. And it largely did :)

I stated right out of the gate that it was not to be merged and that "we" needed to work on it. I said we because ultimately you are the one that is going to have to maintain it so you need to know how it works. while I have been making most of the changes the changes I am making are to simplify it so it will be less of a headache should a bug show up or if you need to add something to it.

I often find that reviewing existing code (or bugfixing) takes up much more time than actually writing the code which is why I want to have everything tested. And not just small unit tests, but large integration tests as well. That way I know how the code is supposed to behave and what results are expected. That way I know for certain that a bug fix won't break any existing behaviour.
Also... every bug report should result in a few new tests for that specific case.

As 2.6.3 + e2ed00ac is OK now I'm closing this ticket.
Thank you


Improve travis testing

Hi there! I tried a few differents things and approaches looking forward to have a consistent suite test at least running in Travis-CI, despite all the effort they are still failing every now and then (I try them also locally running their docker image, and never got a failure).
This PR propose some changes that help to run them almost correct on CI
Happy to discuss other attempts or any other approaches, this are the things that this PR includes:

Remove the downloaded local dynamoDB and add the install script in travis do download the latest and use it
Bundle the gemfile in travis
Add the gem install bundler because jruby-head seems to don't have it on travis-CI.
Update the README with the new way to run the tests
Change the start_dynamodblocal script to use -dbPath instead of -inMemory to avoid Travis-CI from killing the process. This make the tests a little bit slowers though! :worried:
Add a call on each spec to ennsuring that DynamoDB is runing  and if not start it again! This allows to quickly realize which spec is the responsible
Update & Tweak some specs to use let() instead of let!() to improve memory usage

Feel free to let me know anything that you may found that can improve this
Thanks!

Coverage increased (+0.4%) to 95.877% when pulling f63006bf66c8d6015226e47abf96a70453c2673e on cavi21:improve_travis_testing into 81c74544d05f3ff146da46747bea168858ea8f2d on Dynamoid:master.

Coverage increased (+0.1%) to 95.589% when pulling c3b6a7e3aac15e46575eedcf0f2b9bf773df5699 on cavi21:improve_travis_testing into 81c74544d05f3ff146da46747bea168858ea8f2d on Dynamoid:master.

Coverage decreased (-0.3%) to 95.164% when pulling c6788e3c60aa04cc189ac0eaa9b8df3c3c7292c2 on cavi21:improve_travis_testing into 81c74544d05f3ff146da46747bea168858ea8f2d on Dynamoid:master.

At present, I'm hacking around trying to figure out how to test my Rails app built on Dyanmoid/Dynamo... not intuitive.
Any suggestions from the pros? Thanks!
(I'm happy to consolidate suggestions and add to the README!)

@cavi21, that is beautiful. Thank you.

Awesome @philipmw! There is still a weird issue with ruby 2.2.2 in Travis, seems that it consumes a lot of memory and kill the DynamoDB instance, I erratically got those errors and restart the build (sometimes works, I'll love to find that issue though! haha)


Running npm run stage:save clears out work

I am following along the book. After running the stage switch command and choosing to work in the chapter 3 start and coding in chapter three start, when I run npm run stage:save and confirm the changes, all progress is being wiped out in the chapter three start dir. I am never seeing the changes in the updated src. Where am I screwing up in the workflow?

Hey @micahrcorn , that's very strange. Anything you modify in the src should get copied to code-stages/chapter-03-start upon saving. Are you saying that the content from code-stages/chapter-03-start gets deleted, and remains empty?
Can you provide more info, such as the steps you made, the outputs you received in the console, and what OS and Node version you are using?

Aight, so I run  npm run stage:switch and choose chapter-03-start and npm run dev to spin it up. I read the README and it states The files of the selected chapter will be copied to the main directory. You can now start working on the code.
Currently it is unclear in my ide Webstorm node 19..6.1``mac m2 ventura what is the main directory I am supposed to be working in. I assumed that I would be working inside of the chapter-03-start/src dir, and those saves would show up in the top level ignored dir src. I could be totally off in assuming this.  When making changes in the working dir chapter-03-start/src and then running npm run stage:save I wasn't seeing any change in the top level src.

Ok, here is how it works:
To make it simpler to maintain dependencies and do a single "npm install" for all the chapters, we have the code-stages folder, which keeps code versions of each chapter since each chapter needs some preparations.
When you execute npm run stage:switch and choose a version, that version gets copied into the main directory which is the root of the whole project. Notice how each chapter has its own src. Well, that gets copied into the root and you start working with it.
To avoid messing up the progress of each chapter, and to keep track of the changes easier, the src folder is git ignored. But since some people might want to save their current progress, we have the stage:save command which will take what's in the main directory and copy in the code-stages version. For example, if you chose to work on chapter-03-start, when you run stage:save - the src folder will update what's in code-stages/chapter-03-start, and those changes will be tracked by Git.

Right on! I see the ide is warning me that I am editing an ignored file, but it actually isn't. This is a bit confusing but thanks for explaining. Loving what I see so far in the material! Good Job.

Thanks, happy you hear you love the content :)
Btw, if you really want to track the src folder, you can do that by removing or commenting out line 50 in .gitignore.


Implement Amazon Glue service

What problem are you facing?
Amazon Glue resources are missing.
https://docs.aws.amazon.com/sdk-for-go/api/service/glue/
How could Crossplane help solve your problem?
Use ACK to generate glue service and then fill the gaps.

look forward for this service


Crash on Origins screen

here's the crash log
https://pastebin.com/Ut2SCwea

I've not been able to recreate this crash in 1.21, if this is still something you're getting please reopen this issue.
Sorry for the late response


Docs: faster onboarding, identify running processes, improve internal proxy clarification

uh, I now see the merging issues. That's why I saw differences with the master ones.

Fixed the merge conflict this weekend, enough small text tinkering for now.  Quick review and then merge? I see another PR/mentionning of the grander docs integration  as well coming up.

@fredvd watch out, we are about to merge https://github.com/plone/volto/pull/3001 !

@sneridagh I'm not merging my own PR's. But this one is ready.

@fredvd ok, let's do this, since the merge looks good, let's merge this one. Then https://github.com/plone/volto/pull/3001
/cc @stevepiercy

This looks good to me.
#3001 has more work ahead and is not ready for release, unless you don't care about docs that will not automatically build and deploy to production.
There will need to be some merging, cherry-picking, or rebasing, no matter what. I'd suggest having two deployments in parallel, and port doc changes from master to plone6-docs. Please let me know.


False positive of UnnecessaryApply when using this

PassengerSelectorDialogFragment().newInstance(it.copy()).apply {
  show(supportFragmentManager, this.tag)
}

get's flagged with 1.0.0
It should not though since I'm getting the tag from this which is only applicable when I'm using apply

I just added this test to UnnecessaryApplySpec expecting it to fail but it passes:
            it("should not report when 'this' referenced more than once") {
                assertThat(subject.lint("""
                    PassengerSelectorDialogFragment().newInstance(it.copy()).apply {
                        show(supportFragmentManager, this.tag)
                    }
                """)).isEmpty()
            }

Weird. 1.0.0 fails for me on the code base. But then again, I'm no longer working on that code base so :man_shrugging:

I'm going to close this then - if you can replicate or come across a similar example please reply here and we can take a look. Thanks!

Yo!


Change the project management

This PR aims to change the last way to manage the project (using requirements.txt) using uv.

It seems that in the case of linux (archlinux is my case), installing pipx:
sudo pacman -S python-pipx
and then uv:
pipx install uv
is a better practice.