>>> py3-pyroma: Building testing/py3-pyroma 2.6-r5 (using abuild 3.12.0-r5) started Mon, 15 Apr 2024 20:24:30 +0000 >>> py3-pyroma: Checking sanity of /home/buildozer/aports/testing/py3-pyroma/APKBUILD... >>> py3-pyroma: Analyzing dependencies... >>> py3-pyroma: Installing for build: build-base py3-pygments py3-setuptools py3-docutils python3-dev (1/24) Installing libbz2 (1.0.8-r6) (2/24) Installing libffi (3.4.6-r0) (3/24) Installing gdbm (1.23-r1) (4/24) Installing xz-libs (5.6.1-r3) (5/24) Installing mpdecimal (4.0.0-r0) (6/24) Installing libpanelw (6.4_p20240330-r0) (7/24) Installing readline (8.2.10-r0) (8/24) Installing sqlite-libs (3.45.2-r0) (9/24) Installing python3 (3.12.3-r0) (10/24) Installing python3-pycache-pyc0 (3.12.3-r0) (11/24) Installing pyc (3.12.3-r0) (12/24) Installing py3-pygments-pyc (2.17.2-r1) (13/24) Installing python3-pyc (3.12.3-r0) (14/24) Installing py3-pygments (2.17.2-r1) (15/24) Installing py3-parsing (3.1.2-r1) (16/24) Installing py3-parsing-pyc (3.1.2-r1) (17/24) Installing py3-packaging (24.0-r1) (18/24) Installing py3-packaging-pyc (24.0-r1) (19/24) Installing py3-setuptools (69.2.0-r2) (20/24) Installing py3-setuptools-pyc (69.2.0-r2) (21/24) Installing py3-docutils (0.20.1-r2) (22/24) Installing py3-docutils-pyc (0.20.1-r2) (23/24) Installing python3-dev (3.12.3-r0) (24/24) Installing .makedepends-py3-pyroma (20240415.202432) Executing busybox-1.36.1-r25.trigger OK: 521 MiB in 131 packages >>> py3-pyroma: Cleaning up srcdir >>> py3-pyroma: Cleaning up pkgdir >>> py3-pyroma: Cleaning up tmpdir >>> py3-pyroma: Fetching https://distfiles.alpinelinux.org/distfiles/edge//py3-pyroma-2.6.tar.gz >>> py3-pyroma: Fetching https://distfiles.alpinelinux.org/distfiles/edge//py3-pyroma-2.6.tar.gz >>> py3-pyroma: Checking sha512sums... py3-pyroma-2.6.tar.gz: OK >>> py3-pyroma: Unpacking /var/cache/distfiles/edge/py3-pyroma-2.6.tar.gz... running build running build_py creating build creating build/lib creating build/lib/pyroma copying pyroma/__init__.py -> build/lib/pyroma copying pyroma/pypidata.py -> build/lib/pyroma copying pyroma/classifiers.py -> build/lib/pyroma copying pyroma/tests.py -> build/lib/pyroma copying pyroma/ratings.py -> build/lib/pyroma copying pyroma/projectdata.py -> build/lib/pyroma copying pyroma/distributiondata.py -> build/lib/pyroma running egg_info creating pyroma.egg-info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt writing manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pyroma.testdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete' 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 'pyroma.testdata.complete' 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 'pyroma.testdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete' 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 'pyroma.testdata.complete.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete.complete' 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 'pyroma.testdata.complete.complete' 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 'pyroma.testdata.complete.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete.complete' 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 'pyroma.testdata.custom_test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_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 'pyroma.testdata.custom_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 'pyroma.testdata.custom_test' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_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 'pyroma.testdata.custom_test.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test.minimal' 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 'pyroma.testdata.custom_test.minimal' 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 'pyroma.testdata.custom_test.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test.minimal' 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 'pyroma.testdata.distributions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.distributions' 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 'pyroma.testdata.distributions' 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 'pyroma.testdata.distributions' to be distributed and are already explicitly excluding 'pyroma.testdata.distributions' 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 'pyroma.testdata.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking' 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 'pyroma.testdata.lacking' 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 'pyroma.testdata.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking' 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 'pyroma.testdata.lacking.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking.lacking' 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 'pyroma.testdata.lacking.lacking' 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 'pyroma.testdata.lacking.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking.lacking' 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 'pyroma.testdata.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal' 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 'pyroma.testdata.minimal' 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 'pyroma.testdata.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal' 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 'pyroma.testdata.minimal.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal.minimal' 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 'pyroma.testdata.minimal.minimal' 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 'pyroma.testdata.minimal.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal.minimal' 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 'pyroma.testdata.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config' 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 'pyroma.testdata.only_config' 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 'pyroma.testdata.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config' 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 'pyroma.testdata.only_config.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config.only_config' 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 'pyroma.testdata.only_config.only_config' 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 'pyroma.testdata.only_config.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config.only_config' 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 'pyroma.testdata.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config' 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 'pyroma.testdata.setup_config' 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 'pyroma.testdata.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config' 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 'pyroma.testdata.setup_config.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config.setup_config' 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 'pyroma.testdata.setup_config.setup_config' 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 'pyroma.testdata.setup_config.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config.setup_config' 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 'pyroma.testdata.xmlrpcdata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata' 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 'pyroma.testdata.xmlrpcdata' 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 'pyroma.testdata.xmlrpcdata' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata' 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 'pyroma.testdata.xmlrpcdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.complete' 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 'pyroma.testdata.xmlrpcdata.complete' 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 'pyroma.testdata.xmlrpcdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.complete' 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 'pyroma.testdata.xmlrpcdata.distribute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.distribute' 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 'pyroma.testdata.xmlrpcdata.distribute' 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 'pyroma.testdata.xmlrpcdata.distribute' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.distribute' 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) creating build/lib/pyroma/testdata creating build/lib/pyroma/testdata/complete copying pyroma/testdata/complete/README.txt -> build/lib/pyroma/testdata/complete copying pyroma/testdata/complete/setup.cfg -> build/lib/pyroma/testdata/complete copying pyroma/testdata/complete/setup.py -> build/lib/pyroma/testdata/complete creating build/lib/pyroma/testdata/complete/complete copying pyroma/testdata/complete/complete/__init__.py -> build/lib/pyroma/testdata/complete/complete copying pyroma/testdata/complete/complete/tests.py -> build/lib/pyroma/testdata/complete/complete creating build/lib/pyroma/testdata/custom_test copying pyroma/testdata/custom_test/setup.cfg -> build/lib/pyroma/testdata/custom_test copying pyroma/testdata/custom_test/setup.py -> build/lib/pyroma/testdata/custom_test creating build/lib/pyroma/testdata/custom_test/minimal copying pyroma/testdata/custom_test/minimal/__init__.py -> build/lib/pyroma/testdata/custom_test/minimal creating build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar -> build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar.bz2 -> build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar.gz -> build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.zip -> build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/distribute-0.6.15.tar.gz -> build/lib/pyroma/testdata/distributions creating build/lib/pyroma/testdata/lacking copying pyroma/testdata/lacking/setup.cfg -> build/lib/pyroma/testdata/lacking copying pyroma/testdata/lacking/setup.py -> build/lib/pyroma/testdata/lacking creating build/lib/pyroma/testdata/lacking/lacking copying pyroma/testdata/lacking/lacking/__init__.py -> build/lib/pyroma/testdata/lacking/lacking creating build/lib/pyroma/testdata/minimal copying pyroma/testdata/minimal/setup.cfg -> build/lib/pyroma/testdata/minimal copying pyroma/testdata/minimal/setup.py -> build/lib/pyroma/testdata/minimal creating build/lib/pyroma/testdata/minimal/minimal copying pyroma/testdata/minimal/minimal/__init__.py -> build/lib/pyroma/testdata/minimal/minimal creating build/lib/pyroma/testdata/only_config copying pyroma/testdata/only_config/README.txt -> build/lib/pyroma/testdata/only_config copying pyroma/testdata/only_config/setup.cfg -> build/lib/pyroma/testdata/only_config creating build/lib/pyroma/testdata/only_config/only_config copying pyroma/testdata/only_config/only_config/__init__.py -> build/lib/pyroma/testdata/only_config/only_config creating build/lib/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/README.txt -> build/lib/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/setup.cfg -> build/lib/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/setup.py -> build/lib/pyroma/testdata/setup_config creating build/lib/pyroma/testdata/setup_config/setup_config copying pyroma/testdata/setup_config/setup_config/__init__.py -> build/lib/pyroma/testdata/setup_config/setup_config creating build/lib/pyroma/testdata/xmlrpcdata copying pyroma/testdata/xmlrpcdata/completedata.py -> build/lib/pyroma/testdata/xmlrpcdata copying pyroma/testdata/xmlrpcdata/distributedata.py -> build/lib/pyroma/testdata/xmlrpcdata creating build/lib/pyroma/testdata/xmlrpcdata/complete copying pyroma/testdata/xmlrpcdata/complete/1.0.dev1.html -> build/lib/pyroma/testdata/xmlrpcdata/complete creating build/lib/pyroma/testdata/xmlrpcdata/distribute copying pyroma/testdata/xmlrpcdata/distribute/0.6.15.html -> build/lib/pyroma/testdata/xmlrpcdata/distribute running test WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. /usr/lib/python3.12/site-packages/setuptools/command/test.py:193: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! ir_d = dist.fetch_build_eggs(dist.install_requires) WARNING: The wheel package is not available. /usr/lib/python3.12/site-packages/setuptools/command/test.py:194: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! tr_d = dist.fetch_build_eggs(dist.tests_require or []) WARNING: The wheel package is not available. /usr/lib/python3.12/site-packages/setuptools/command/test.py:195: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! er_d = dist.fetch_build_eggs( WARNING: The wheel package is not available. running egg_info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' running build_ext test_complete (pyroma.tests.DistroDataTest.test_complete) ... /usr/lib/python3.12/tarfile.py:2221: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior. warnings.warn( /home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/distributiondata.py:22: ResourceWarning: unclosed file <_io.BufferedReader name='/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/testdata/distributions/complete-1.0.dev1.tar'> tarfile.open(name=path, mode="r:*").extractall(tempdir) ResourceWarning: Enable tracemalloc to get the object allocation traceback /usr/lib/python3.12/site-packages/setuptools/__init__.py:81: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) WARNING: The wheel package is not available. FAIL test_complete (pyroma.tests.ProjectDataTest.test_complete) ... WARNING: The wheel package is not available. FAIL test_complete (pyroma.tests.PyPITest.test_complete) ... /home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/tests.py:96: ResourceWarning: unclosed file <_io.TextIOWrapper name='/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/testdata/xmlrpcdata/completedata.py' mode='rt' encoding='UTF-8'> exec(open(filename, "rt").read(), None, data) ResourceWarning: Enable tracemalloc to get the object allocation traceback /home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/tests.py:57: ResourceWarning: unclosed file <_io.BufferedReader name='/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/testdata/distributions/complete-1.0.dev1.tar.gz'> return open(self.filename, "rb").read() ResourceWarning: Enable tracemalloc to get the object allocation traceback WARNING: The wheel package is not available. ok test_distribute (pyroma.tests.PyPITest.test_distribute) ... /home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/tests.py:96: ResourceWarning: unclosed file <_io.TextIOWrapper name='/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/testdata/xmlrpcdata/distributedata.py' mode='rt' encoding='UTF-8'> exec(open(filename, "rt").read(), None, data) ResourceWarning: Enable tracemalloc to get the object allocation traceback /home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/tests.py:57: ResourceWarning: unclosed file <_io.BufferedReader name='/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/testdata/distributions/distribute-0.6.15.tar.gz'> return open(self.filename, "rb").read() ResourceWarning: Enable tracemalloc to get the object allocation traceback /usr/lib/python3.12/tarfile.py:2221: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior. warnings.warn( :13: ResourceWarning: unclosed file <_io.TextIOWrapper name='MANIFEST.in' mode='r' encoding='UTF-8'> ResourceWarning: Enable tracemalloc to get the object allocation traceback creating build creating build/src creating build/src/docs creating build/src/docs/_templates creating build/src/docs/_theme creating build/src/docs/_theme/nature creating build/src/docs/_theme/nature/static creating build/src/setuptools creating build/src/setuptools/command creating build/src/setuptools/tests creating build/src/setuptools/tests/indexes creating build/src/setuptools/tests/indexes/test_links_priority creating build/src/setuptools/tests/indexes/test_links_priority/simple creating build/src/setuptools/tests/indexes/test_links_priority/simple/foobar creating build/src/tests creating build/src/tests/shlib_test copying setuptools/archive_util.py -> build/src/setuptools copying setuptools/__init__.py -> build/src/setuptools copying setuptools/sandbox.py -> build/src/setuptools copying setuptools/dist.py -> build/src/setuptools copying setuptools/package_index.py -> build/src/setuptools copying setuptools/depends.py -> build/src/setuptools copying setuptools/extension.py -> build/src/setuptools copying setuptools/command/install.py -> build/src/setuptools/command copying setuptools/command/build_py.py -> build/src/setuptools/command copying setuptools/command/upload_docs.py -> build/src/setuptools/command copying setuptools/command/develop.py -> build/src/setuptools/command copying setuptools/command/install_egg_info.py -> build/src/setuptools/command copying setuptools/command/__init__.py -> build/src/setuptools/command copying setuptools/command/build_ext.py -> build/src/setuptools/command copying setuptools/command/bdist_rpm.py -> build/src/setuptools/command copying setuptools/command/test.py -> build/src/setuptools/command copying setuptools/command/register.py -> build/src/setuptools/command copying setuptools/command/upload.py -> build/src/setuptools/command copying setuptools/command/bdist_egg.py -> build/src/setuptools/command copying setuptools/command/install_lib.py -> build/src/setuptools/command copying setuptools/command/egg_info.py -> build/src/setuptools/command copying setuptools/command/easy_install.py -> build/src/setuptools/command copying setuptools/command/setopt.py -> build/src/setuptools/command copying setuptools/command/saveopts.py -> build/src/setuptools/command copying setuptools/command/bdist_wininst.py -> build/src/setuptools/command copying setuptools/command/sdist.py -> build/src/setuptools/command copying setuptools/command/install_scripts.py -> build/src/setuptools/command copying setuptools/command/alias.py -> build/src/setuptools/command copying setuptools/command/rotate.py -> build/src/setuptools/command copying setuptools/tests/test_upload_docs.py -> build/src/setuptools/tests copying setuptools/tests/__init__.py -> build/src/setuptools/tests copying setuptools/tests/test_develop.py -> build/src/setuptools/tests copying setuptools/tests/test_easy_install.py -> build/src/setuptools/tests copying setuptools/tests/test_build_ext.py -> build/src/setuptools/tests copying setuptools/tests/doctest.py -> build/src/setuptools/tests copying setuptools/tests/test_packageindex.py -> build/src/setuptools/tests copying setuptools/tests/server.py -> build/src/setuptools/tests copying setuptools/tests/test_sandbox.py -> build/src/setuptools/tests copying setuptools/tests/test_resources.py -> build/src/setuptools/tests copying setuptools/tests/win_script_wrapper.txt -> build/src/setuptools/tests copying setuptools/cli.exe -> build/src/setuptools copying setuptools/gui.exe -> build/src/setuptools copying tests/test_distribute_setup.py -> build/src/tests copying tests/manual_test.py -> build/src/tests copying tests/install_test.py -> build/src/tests copying tests/shlib_test/setup.py -> build/src/tests/shlib_test copying tests/shlib_test/test_hello.py -> build/src/tests/shlib_test copying tests/shlib_test/hello.c -> build/src/tests/shlib_test copying tests/shlib_test/hellolib.c -> build/src/tests/shlib_test copying tests/shlib_test/hello.pyx -> build/src/tests/shlib_test copying tests/api_tests.txt -> build/src/tests :24: DeprecationWarning: lib2to3 package is deprecated and may not be able to parse Python 3.10+ Skipping optional fixer: buffer Skipping optional fixer: idioms Skipping optional fixer: set_literal Skipping optional fixer: ws_comma Refactored build/src/tests/api_tests.txt --- build/src/tests/api_tests.txt (original) +++ build/src/tests/api_tests.txt (refactored) @@ -39,7 +39,7 @@ >>> dist.py_version == sys.version[:3] True - >>> print dist.platform + >>> print(dist.platform) None Including various computed attributes:: @@ -199,7 +199,7 @@ You can ask a WorkingSet to ``find()`` a distribution matching a requirement:: >>> from pkg_resources import Requirement - >>> print ws.find(Requirement.parse("Foo==1.0")) # no match, return None + >>> print(ws.find(Requirement.parse("Foo==1.0"))) # no match, return None None >>> ws.find(Requirement.parse("Bar==0.9")) # match, return distribution @@ -211,7 +211,7 @@ >>> try: ... ws.find(Requirement.parse("Bar==1.0")) ... except VersionConflict: - ... print 'ok' + ... print('ok') ok You can subscribe a callback function to receive notifications whenever a new @@ -219,7 +219,7 @@ once for each existing distribution in the working set, and then is called again for new distributions added thereafter:: - >>> def added(dist): print "Added", dist + >>> def added(dist): print("Added", dist) >>> ws.subscribe(added) Added Bar 0.9 >>> foo12 = Distribution(project_name="Foo", version="1.2", location="f12") Files that were modified: build/src/tests/api_tests.txt copying setuptools/tests/indexes/test_links_priority/external.html -> build/src/setuptools/tests/indexes/test_links_priority copying setuptools/tests/indexes/test_links_priority/simple/foobar/index.html -> build/src/setuptools/tests/indexes/test_links_priority/simple/foobar copying docs/conf.py -> build/src/docs copying docs/setuptools.txt -> build/src/docs copying docs/easy_install.txt -> build/src/docs copying docs/python3.txt -> build/src/docs copying docs/using.txt -> build/src/docs copying docs/index.txt -> build/src/docs copying docs/pkg_resources.txt -> build/src/docs copying docs/roadmap.txt -> build/src/docs copying docs/_theme/nature/theme.conf -> build/src/docs/_theme/nature copying docs/_theme/nature/static/pygments.css -> build/src/docs/_theme/nature/static copying docs/_theme/nature/static/nature.css_t -> build/src/docs/_theme/nature/static copying docs/Makefile -> build/src/docs copying docs/_templates/indexsidebar.html -> build/src/docs/_templates copying pkg_resources.py -> build/src copying distribute_setup.py -> build/src copying site.py -> build/src copying easy_install.py -> build/src copying setup.py -> build/src copying CHANGES.txt -> build/src copying DEVGUIDE.txt -> build/src copying CONTRIBUTORS.txt -> build/src copying README.txt -> build/src copying MANIFEST.in -> build/src copying launcher.c -> build/src /home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py:131: DeprecationWarning: The 'warn' function is deprecated, use 'warning' instead logging.warn("Exception when running setup.", exc_info=True) Exception when running setup. Traceback (most recent call last): File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py", line 124, in run_setup exec(f.read(), glocals, glocals) File "", line 27, in AttributeError: module 'distutils.util' has no attribute 'run_2to3' ok test_complete (pyroma.tests.RatingsTest.test_complete) ... /usr/lib/python3.12/site-packages/setuptools/__init__.py:81: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) WARNING: The wheel package is not available. ok test_custom_test (pyroma.tests.RatingsTest.test_custom_test) ... /home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py:131: DeprecationWarning: The 'warn' function is deprecated, use 'warning' instead logging.warn("Exception when running setup.", exc_info=True) Exception when running setup. Traceback (most recent call last): File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py", line 124, in run_setup exec(f.read(), glocals, glocals) File "", line 11, in File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py", line 43, in setuptools_setup_replacement self._setuptools_setup(**kw) File "/usr/lib/python3.12/site-packages/setuptools/__init__.py", line 104, in setup return distutils.core.setup(**attrs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py", line 39, in distutils_setup_replacement self._distutils_setup(**kw) File "/usr/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 147, in setup _setup_distribution = dist = klass(attrs) ^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/setuptools/dist.py", line 318, in __init__ self.metadata.version = self._normalize_version(self.metadata.version) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/setuptools/dist.py", line 354, in _normalize_version normalized = str(Version(version)) ^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/setuptools/_vendor/packaging/version.py", line 198, in __init__ raise InvalidVersion(f"Invalid version: '{version}'") setuptools.extern.packaging.version.InvalidVersion: Invalid version: '0.0foo' FAIL test_lacking (pyroma.tests.RatingsTest.test_lacking) ... ok test_markdown (pyroma.tests.RatingsTest.test_markdown) ... ok test_minimal (pyroma.tests.RatingsTest.test_minimal) ... /home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py:131: DeprecationWarning: The 'warn' function is deprecated, use 'warning' instead logging.warn("Exception when running setup.", exc_info=True) Exception when running setup. Traceback (most recent call last): File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py", line 124, in run_setup exec(f.read(), glocals, glocals) File "", line 5, in File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py", line 43, in setuptools_setup_replacement self._setuptools_setup(**kw) File "/usr/lib/python3.12/site-packages/setuptools/__init__.py", line 104, in setup return distutils.core.setup(**attrs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py", line 39, in distutils_setup_replacement self._distutils_setup(**kw) File "/usr/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 147, in setup _setup_distribution = dist = klass(attrs) ^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/setuptools/dist.py", line 318, in __init__ self.metadata.version = self._normalize_version(self.metadata.version) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/setuptools/dist.py", line 354, in _normalize_version normalized = str(Version(version)) ^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/setuptools/_vendor/packaging/version.py", line 198, in __init__ raise InvalidVersion(f"Invalid version: '{version}'") setuptools.extern.packaging.version.InvalidVersion: Invalid version: '0.0foo' FAIL test_only_config (pyroma.tests.RatingsTest.test_only_config) ... /home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/projectdata.py:179: SetuptoolsDeprecationWarning: Deprecated API usage. !! ******************************************************************************** As setuptools moves its configuration towards `pyproject.toml`, `setuptools.config.read_configuration` became deprecated. For the time being, you can use the `setuptools.config.setupcfg` module to access a backward compatible API, but this module is provisional and might be removed in the future. To read project metadata, consider using ``build.util.project_wheel_metadata`` (https://pypi.org/project/build/). For simple scenarios, you can also try parsing the file directly with the help of ``configparser``. ******************************************************************************** !! data = config.read_configuration("setup.cfg") ok test_setup_config (pyroma.tests.RatingsTest.test_setup_config) ... ok ====================================================================== FAIL: test_complete (pyroma.tests.DistroDataTest.test_complete) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/tests.py", line 309, in test_complete self.assertEqual(data, COMPLETE) AssertionError: {'_se[51 chars]0', 'author': 'Lennart Regebro', 'author_email[2029 chars]ete'} != {'_se[51 chars]0', 'description': 'This is a test package for[1993 chars]ete'} Diff is 3276 characters long. Set self.maxDiff to None to see it. ====================================================================== FAIL: test_complete (pyroma.tests.ProjectDataTest.test_complete) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/tests.py", line 297, in test_complete self.assertEqual(data, COMPLETE) AssertionError: {'_se[51 chars]0', 'author': 'Lennart Regebro', 'author_email[2029 chars]ete'} != {'_se[51 chars]0', 'description': 'This is a test package for[1993 chars]ete'} {'_setuptools': True, 'author': 'Lennart Regebro', 'author_email': 'regebro@gmail.com', 'classifiers': ['Development Status :: 6 - Mature', 'Operating System :: OS Independent', 'Programming Language :: Python :: 2.6', 'Programming Language :: Python :: 2.7', 'Programming Language :: Python :: 3.1', 'Programming Language :: Python :: 3.2', 'Programming Language :: Python :: 3.3', 'License :: OSI Approved :: MIT License'], 'description': 'This is a test package for pyroma.', - 'install_requires': ['zope.event'], 'keywords': ['pypi', 'quality', 'example'], 'license': 'MIT', 'long_description': 'Complete\n' '========\n' '\n' 'This is a test package for pyroma that is supposed to ' 'have a complete\n' 'set of metadata and also runnable tests. It should score ' 'the maximum possible\n' 'on package tests.\n' '\n' 'Lorem ipsum dolor sit amet, consectetur adipiscing elit. ' 'Sed porttitor, neque at\n' 'dignissim condimentum, libero est dictum dolor, sit amet ' 'tempor urna diam eget\n' 'velit. Suspendisse at odio quam, ut vestibulum ipsum. ' 'Nulla facilisi. Nullam\n' 'nunc dolor, tempus in vulputate id, fringilla eget ' 'metus. Pellentesque nulla\n' 'nisl, imperdiet ac vulputate non, commodo tincidunt ' 'purus. Aenean sollicitudin\n' 'orci eget diam dignissim scelerisque. Donec quis neque ' 'nisl, eu adipiscing\n' 'velit. Aenean convallis ante sapien. Etiam vitae viverra ' 'libero. Nullam ac\n' 'ligula erat. Aliquam pellentesque, est eget faucibus ' 'pharetra, urna orci rhoncus\n' 'nisi, adipiscing elementum libero lectus ut odio. Duis ' 'tincidunt mi quam, quis\n' 'interdum enim. Nunc sed urna urna, id lacinia turpis. ' 'Quisque malesuada, velit\n' 'ut tincidunt lacinia, dolor augue varius velit, in ' 'ultrices lectus enim et\n' 'dolor. Fusce augue eros, aliquet ac dapibus at, ' 'tincidunt vitae leo. Lorem ipsum\n' 'dolor sit amet, consectetur adipiscing elit. Vivamus ' 'sapien neque, fermentum sed\n' 'ultrices sit amet, fermentum nec est. Pellentesque ' 'imperdiet enim nec velit\n' 'posuere id dignissim massa molestie.\n', 'name': 'complete', 'project_urls': {'Source Code': 'https://github.com/regebro/pyroma'}, 'test_suite': 'complete', 'url': 'https://github.com/regebro/pyroma', 'version': '1.0', 'zip_safe': True} ====================================================================== FAIL: test_custom_test (pyroma.tests.RatingsTest.test_custom_test) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/tests.py", line 207, in test_custom_test self.assertEqual( AssertionError: Tuples differ: (10, []) != (2, ["The package's version number does no[716 chars]s.']) First differing element 0: 10 2 Diff is 834 characters long. Set self.maxDiff to None to see it. ====================================================================== FAIL: test_minimal (pyroma.tests.RatingsTest.test_minimal) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/buildozer/aports/testing/py3-pyroma/src/pyroma-2.6/pyroma/tests.py", line 159, in test_minimal self.assertEqual( AssertionError: Tuples differ: (0, ['The package had no description!', "T[730 chars]s.']) != (2, ["The package's version number does no[716 chars]s.']) First differing element 0: 0 2 Diff is 997 characters long. Set self.maxDiff to None to see it. ---------------------------------------------------------------------- Ran 11 tests in 0.413s FAILED (failures=4) Test failed: error: Test failed: >>> ERROR: py3-pyroma: check failed >>> py3-pyroma: Uninstalling dependencies... (1/24) Purging .makedepends-py3-pyroma (20240415.202432) (2/24) Purging py3-pygments-pyc (2.17.2-r1) (3/24) Purging py3-pygments (2.17.2-r1) (4/24) Purging py3-setuptools-pyc (69.2.0-r2) (5/24) Purging py3-setuptools (69.2.0-r2) (6/24) Purging py3-packaging-pyc (24.0-r1) (7/24) Purging py3-packaging (24.0-r1) (8/24) Purging py3-parsing-pyc (3.1.2-r1) (9/24) Purging py3-parsing (3.1.2-r1) (10/24) Purging py3-docutils-pyc (0.20.1-r2) (11/24) Purging py3-docutils (0.20.1-r2) (12/24) Purging python3-dev (3.12.3-r0) (13/24) Purging python3-pyc (3.12.3-r0) (14/24) Purging python3-pycache-pyc0 (3.12.3-r0) (15/24) Purging pyc (3.12.3-r0) (16/24) Purging python3 (3.12.3-r0) (17/24) Purging gdbm (1.23-r1) (18/24) Purging libbz2 (1.0.8-r6) (19/24) Purging libffi (3.4.6-r0) (20/24) Purging libpanelw (6.4_p20240330-r0) (21/24) Purging mpdecimal (4.0.0-r0) (22/24) Purging readline (8.2.10-r0) (23/24) Purging sqlite-libs (3.45.2-r0) (24/24) Purging xz-libs (5.6.1-r3) Executing busybox-1.36.1-r25.trigger OK: 346 MiB in 107 packages