Arch Linux User Repository

Ahoj,

your package installs some generic files that should not be installed and lead to conflict with other packages that do the same mistake:

error: failed to commit transaction (conflicting files)
python-tr064: /usr/lib/python3.12/site-packages/tests/__init__.py exists in filesystem (owned by kicost-git)
python-tr064: /usr/lib/python3.12/site-packages/tests/__pycache__/__init__.cpython-312.opt-1.pyc exists in filesystem (owned by kicost-git)
python-tr064: /usr/lib/python3.12/site-packages/tests/__pycache__/__init__.cpython-312.pyc exists in filesystem (owned by kicost-git)
Errors occurred, no packages were upgraded.

Regards and thanks for the package!

Additional to this, I get the following warnings:

==> Starting package()...
/usr/lib/python3.12/site-packages/setuptools/dist.py:472: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!

        ********************************************************************************
        Usage of dash-separated 'description-file' will not be supported in future
        versions. Please use the underscore name 'description_file' instead.

        By 2024-Sep-26, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  opt = self.warn_dash_deprecation(opt, section)
[...]
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.configs' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.configs' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.configs' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.configs' to be distributed and are
        already explicitly excluding 'tests.configs' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.digikey' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.digikey' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.digikey' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.digikey' to be distributed and are
        already explicitly excluding 'tests.digikey' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.discard' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.discard' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.discard' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.discard' to be distributed and are
        already explicitly excluding 'tests.discard' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.element14' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.element14' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.element14' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.element14' to be distributed and are
        already explicitly excluding 'tests.element14' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.expected_test' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.expected_test' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.expected_test' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.expected_test' to be distributed and are
        already explicitly excluding 'tests.expected_test' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.expected_test_small' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.expected_test_small' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.expected_test_small' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.expected_test_small' to be distributed and are
        already explicitly excluding 'tests.expected_test_small' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.kitspace' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.kitspace' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.kitspace' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.kitspace' to be distributed and are
        already explicitly excluding 'tests.kitspace' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.mouser' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.mouser' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.mouser' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.mouser' to be distributed and are
        already explicitly excluding 'tests.mouser' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.nexar' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.nexar' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.nexar' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.nexar' to be distributed and are
        already explicitly excluding 'tests.nexar' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.nexar_alt' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.nexar_alt' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.nexar_alt' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.nexar_alt' to be distributed and are
        already explicitly excluding 'tests.nexar_alt' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'tests.tme' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'tests.tme' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'tests.tme' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'tests.tme' to be distributed and are
        already explicitly excluding 'tests.tme' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)

Regards!

Ahoj,

you need to change the build process to move away from setup.py and use python-wheel together with python-build and python-installer. See the Arch Linux wiki on python package guidelines.

==> Starting package()...
running install
/usr/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
        ********************************************************************************

!!
  self.initialize_options()

Regards!

A quick fix to fix the generic files in /usr/lib/python3.11/site-packages/tests/ issue (↗ patch to PKGBUILD:

--- PKGBUILD.orig   2023-08-03 14:06:04.397179004 +0200
+++ PKGBUILD    2023-08-03 14:05:09.260508548 +0200
@@ -2,5 +2,5 @@
 pkgname=kicost-git
 _remotename=KiCost
-pkgver=1.1.6.r1.227f246
+pkgver=1.1.18.r1.197a61d
 pkgrel=1
 pkgdesc="Build cost spreadsheet for a KiCad project"
@@ -19,5 +19,7 @@
 makedepends=(
     git
-    python-setuptools
+    python-build
+    python-installer
+    python-wheel
 )
 provides=("${pkgname%-git}")
@@ -34,4 +36,10 @@
 }

+build() {
+    cd "$_remotename"
+
+    python -m build --wheel --no-isolation
+}
+
 check() {
     cd "$_remotename"
@@ -43,4 +51,8 @@
     cd "$_remotename"

-    python setup.py install --root="$pkgdir" --optimize=1
+    _pythonversion="$(python --version | awk '{print $2}' | awk -F. '{print $1"."$2}')"
+    python -m installer --destdir="$pkgdir" --compile-bytecode=2 dist/*.whl
+    rm -Rfv "${pkgdir}/usr/lib/python${_pythonversion}/site-packages/tests"/{__pycache__/{__init__.cpython-*.pyc,dummy-web-server.cpython-*.pyc},__init__.py,dummy-web-server.py}
+
+    install -Dvm644 LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
 }

It might be possible to do it better.

Please review and apply.

Thanks for maintaining!

Errors reported by namcap:

kicost-git E: Missing custom license directory (usr/share/licenses/kicost-git)
kicost-git W: Referenced python module 'urlparse.urlsplit' is an uninstalled dependency (needed in files ['usr/lib/python3.11/site-packages/kicost/distributors/dist_local_template.py'])
kicost-git W: Referenced python module 'urllib2.Request' is an uninstalled dependency (needed in files ['usr/lib/python3.11/site-packages/kicost/distributors/api_tme.py'])
kicost-git W: Referenced python module 'AppKit.NSSearchPathForDirectoriesInDomains' is an uninstalled dependency (needed in files ['usr/lib/python3.11/site-packages/kicost/kicad_config.py'])
kicost-git W: Referenced python module 'urllib2.URLError' is an uninstalled dependency (needed in files ['usr/lib/python3.11/site-packages/kicost/currency_converter/download_rates.py', 'usr/lib/python3.11/site-packages/kicost/distributors/api_tme.py'])
kicost-git W: Referenced python module 'sexpdata' is an uninstalled dependency (needed in files ['usr/lib/python3.11/site-packages/kicost/kicad_config.py'])
kicost-git W: Referenced python module 'urlparse.urlunsplit' is an uninstalled dependency (needed in files ['usr/lib/python3.11/site-packages/kicost/distributors/dist_local_template.py'])
kicost-git W: Referenced python module 'urllib2.urlopen' is an uninstalled dependency (needed in files ['usr/lib/python3.11/site-packages/kicost/currency_converter/download_rates.py', 'usr/lib/python3.11/site-packages/kicost/distributors/api_tme.py'])
kicost-git E: Dependency python-importlib-metadata detected and not included (python modules ['importlib_metadata.distribution'] needed in files ['usr/bin/kicost'])
kicost-git E: Dependency kicad detected and not included (python modules ['pcbnew.ActionPlugin', 'pcbnew.GetBoard'] needed in files ['usr/lib/python3.11/site-packages/kicost/kicost_kicadplugin.py'])
kicost-git E: Dependency python-yaml detected and not included (python modules ['yaml'] needed in files ['usr/lib/python3.11/site-packages/kicost/__main__.py', 'usr/lib/python3.11/site-packages/kicost/config.py'])
kicost-git E: Dependency python-pip detected and not included (python modules ['pip._internal.main', 'pip', 'pip.main'] needed in files ['usr/lib/python3.11/site-packages/kicost/kicost_kicadplugin.py', 'usr/lib/python3.11/site-packages/kicost/kicost_config.py'])
kicost-git E: Dependency python-setuptools detected and not included (python modules ['pkg_resources.load_entry_point'] needed in files ['usr/bin/kicost'])
kicost-git W: Dependency included, but may not be needed ('python-lxml')

Please check which are really applicable, and (selectively) fix.

Thanks for maintaining!

This package installes generic, non-package specific, files, which makes it likely to conflict with other packages:

error: failed to commit transaction (conflicting files)
python-protonvpn-nm-lib: /usr/lib/python3.11/site-packages/tests/__init__.py exists in filesystem (owned by kicost-git)
python-protonvpn-nm-lib: /usr/lib/python3.11/site-packages/tests/__pycache__/__init__.cpython-311.opt-1.pyc exists in filesystem (owned by kicost-git)
python-protonvpn-nm-lib: /usr/lib/python3.11/site-packages/tests/__pycache__/__init__.cpython-311.pyc exists in filesystem (owned by kicost-git)
Errors occurred, no packages were upgraded.

pacman -Ql kicost-git | grep /usr/lib/python3.11/site-packages/tests/ lists me the following files which you need to make sure to get not installed:

/usr/lib/python3.11/site-packages/tests/.gitignore
/usr/lib/python3.11/site-packages/tests/README.md
/usr/lib/python3.11/site-packages/tests/__init__.py
/usr/lib/python3.11/site-packages/tests/__pycache__/__init__.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/tests/__pycache__/__init__.cpython-311.pyc
/usr/lib/python3.11/site-packages/tests/__pycache__/dummy-web-server.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/tests/__pycache__/dummy-web-server.cpython-311.pyc
/usr/lib/python3.11/site-packages/tests/configs/default.yaml
/usr/lib/python3.11/site-packages/tests/dummy-web-server.py
/usr/lib/python3.11/site-packages/tests/expected_test/test.csv
[...]
/usr/lib/python3.11/site-packages/tests/group_1.xml
/usr/lib/python3.11/site-packages/tests/no_empty_overwrite.xml
/usr/lib/python3.11/site-packages/tests/test.cmd
/usr/lib/python3.11/site-packages/tests/test.sh
/usr/lib/python3.11/site-packages/tests/test.xml
/usr/lib/python3.11/site-packages/tests/test2.xml
/usr/lib/python3.11/site-packages/tests/test3.xml

I doubt that anything under /usr/lib/python3.11/site-packages/tests/ is needed at all for this package. Please check if you can remove it or move it to some kicost specific directory.

Please fix!, Regards, thanks for maintaining!

Thanks, updated.

The unit tests seem to require python-requests.