2025-10-16T21:45:13,936 Created temporary directory: /tmp/pip-ephem-wheel-cache-ppskpu6v
2025-10-16T21:45:13,938 Created temporary directory: /tmp/pip-build-tracker-soet21sd
2025-10-16T21:45:13,939 Initialized build tracking at /tmp/pip-build-tracker-soet21sd
2025-10-16T21:45:13,939 Created build tracker: /tmp/pip-build-tracker-soet21sd
2025-10-16T21:45:13,939 Entered build tracker: /tmp/pip-build-tracker-soet21sd
2025-10-16T21:45:13,940 Created temporary directory: /tmp/pip-wheel-9gl0ll77
2025-10-16T21:45:13,944 DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453
2025-10-16T21:45:13,946 Created temporary directory: /tmp/pip-ephem-wheel-cache-1yddkrdr
2025-10-16T21:45:13,971 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
2025-10-16T21:45:13,974 2 location(s) to search for versions of inferno-torch:
2025-10-16T21:45:13,974 * https://pypi.org/simple/inferno-torch/
2025-10-16T21:45:13,974 * https://www.piwheels.org/simple/inferno-torch/
2025-10-16T21:45:13,975 Fetching project page and analyzing links: https://pypi.org/simple/inferno-torch/
2025-10-16T21:45:13,976 Getting page https://pypi.org/simple/inferno-torch/
2025-10-16T21:45:13,977 Found index url https://pypi.org/simple
2025-10-16T21:45:14,191 Fetched page https://pypi.org/simple/inferno-torch/ as application/vnd.pypi.simple.v1+json
2025-10-16T21:45:14,194   Skipping link: No binaries permitted for inferno-torch: https://files.pythonhosted.org/packages/a6/45/b8991c61a9373bb25e8a3e11c84911cb2a85bea4217e412dea2e11e345bd/inferno_torch-0.0.2-py3-none-any.whl (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10)
2025-10-16T21:45:14,195   Found link https://files.pythonhosted.org/packages/a5/f3/03b1637bb22fa9b851c44740a2dcde0aecbc7bacc4f39d4b6a002836cd83/inferno_torch-0.0.2.tar.gz (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10), version: 0.0.2
2025-10-16T21:45:14,196   Skipping link: No binaries permitted for inferno-torch: https://files.pythonhosted.org/packages/16/87/224cf60ae4a629134fce1f852fdb334ed5ea4819437fb05f4f1dce90def4/inferno_torch-0.0.3-py3-none-any.whl (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10)
2025-10-16T21:45:14,197   Found link https://files.pythonhosted.org/packages/92/ab/0e56f7b5c6915af56c8d7f198fa5368dfd1e1a27fa0a179e5764224787a4/inferno_torch-0.0.3.tar.gz (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10), version: 0.0.3
2025-10-16T21:45:14,198   Skipping link: No binaries permitted for inferno-torch: https://files.pythonhosted.org/packages/c6/dc/f7f76c5e32e9a1b3a0b9bf8a271d7a68c20a99dbd86a00ebed0ef7bdfd16/inferno_torch-0.0.4-py3-none-any.whl (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10)
2025-10-16T21:45:14,199   Found link https://files.pythonhosted.org/packages/eb/4b/4d6ed26444e1c2e8da519a7cbe9506f0c2d9e4017fa07c853b078abb1296/inferno_torch-0.0.4.tar.gz (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10), version: 0.0.4
2025-10-16T21:45:14,199   Skipping link: No binaries permitted for inferno-torch: https://files.pythonhosted.org/packages/eb/31/334106263f193e4fe8ccba2da50e0f335ceb2e2a4dfd1e8638ac16ca25fe/inferno_torch-0.0.5-py3-none-any.whl (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10)
2025-10-16T21:45:14,200   Found link https://files.pythonhosted.org/packages/45/b6/811952b738c8ff7a91fee35f4d37f7d60cfbcf65ce3891cff8b7afcd8816/inferno_torch-0.0.5.tar.gz (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10), version: 0.0.5
2025-10-16T21:45:14,201   Skipping link: No binaries permitted for inferno-torch: https://files.pythonhosted.org/packages/b0/af/8c52543d7ef2f300f412b743c60988bc6bb27092d27fd4c1bea4db1b064c/inferno_torch-0.0.6-py3-none-any.whl (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10)
2025-10-16T21:45:14,202   Found link https://files.pythonhosted.org/packages/11/b8/d618b437c79eee753dbb91206c9af7f616f47a673a1273e5cea83e7258a5/inferno_torch-0.0.6.tar.gz (from https://pypi.org/simple/inferno-torch/) (requires-python:>=3.10), version: 0.0.6
2025-10-16T21:45:14,203 Fetching project page and analyzing links: https://www.piwheels.org/simple/inferno-torch/
2025-10-16T21:45:14,204 Getting page https://www.piwheels.org/simple/inferno-torch/
2025-10-16T21:45:14,205 Found index url https://www.piwheels.org/simple
2025-10-16T21:45:14,367 Fetched page https://www.piwheels.org/simple/inferno-torch/ as text/html
2025-10-16T21:45:14,370   Skipping link: No binaries permitted for inferno-torch: https://www.piwheels.org/simple/inferno-torch/inferno_torch-0.0.5-py3-none-any.whl#sha256=09d75ea18d48c2406bc9a0f3f374db6853606952307f7fed531bdba391074e88 (from https://www.piwheels.org/simple/inferno-torch/) (requires-python:>=3.10)
2025-10-16T21:45:14,370   Skipping link: No binaries permitted for inferno-torch: https://www.piwheels.org/simple/inferno-torch/inferno_torch-0.0.4-py3-none-any.whl#sha256=bc2d7c1eaa22f9e4590845d05a1b1926b5408ef53f7615e9ee421a4418f69bce (from https://www.piwheels.org/simple/inferno-torch/) (requires-python:>=3.10)
2025-10-16T21:45:14,371   Skipping link: No binaries permitted for inferno-torch: https://archive1.piwheels.org/simple/inferno-torch/inferno_torch-0.0.3-py3-none-any.whl#sha256=45b75e004bf50d9ce6ea0293ec5d2d3c4889a86d68243db37cf594df1e9502ee (from https://www.piwheels.org/simple/inferno-torch/) (requires-python:>=3.10)
2025-10-16T21:45:14,371   Skipping link: No binaries permitted for inferno-torch: https://archive1.piwheels.org/simple/inferno-torch/inferno_torch-0.0.2-py3-none-any.whl#sha256=4e73ac805744fd361c4e09480a097d83c8630abd132e104cd38d695a23e7180a (from https://www.piwheels.org/simple/inferno-torch/) (requires-python:>=3.10)
2025-10-16T21:45:14,372 Skipping link: not a file: https://www.piwheels.org/simple/inferno-torch/
2025-10-16T21:45:14,373 Skipping link: not a file: https://pypi.org/simple/inferno-torch/
2025-10-16T21:45:14,392 Given no hashes to check 1 links for project 'inferno-torch': discarding no candidates
2025-10-16T21:45:14,410 Collecting inferno-torch==0.0.6
2025-10-16T21:45:14,413   Created temporary directory: /tmp/pip-unpack-jya6y6nv
2025-10-16T21:45:14,549   Downloading inferno_torch-0.0.6.tar.gz (379 kB)
2025-10-16T21:45:14,916   Added inferno-torch==0.0.6 from https://files.pythonhosted.org/packages/11/b8/d618b437c79eee753dbb91206c9af7f616f47a673a1273e5cea83e7258a5/inferno_torch-0.0.6.tar.gz to build tracker '/tmp/pip-build-tracker-soet21sd'
2025-10-16T21:45:14,925   Created temporary directory: /tmp/pip-build-env-0kxzgnu9
2025-10-16T21:45:14,930   Installing build dependencies: started
2025-10-16T21:45:14,931   Running command pip subprocess to install build dependencies
2025-10-16T21:45:16,110   Using pip 23.0.1 from /usr/lib/python3/dist-packages/pip (python 3.11)
2025-10-16T21:45:16,726   DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453
2025-10-16T21:45:16,749   Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
2025-10-16T21:45:18,511   Collecting setuptools>=64
2025-10-16T21:45:18,667     Using cached https://www.piwheels.org/simple/setuptools/setuptools-80.9.0-py3-none-any.whl (1.2 MB)
2025-10-16T21:45:19,070   Collecting setuptools-scm>=8
2025-10-16T21:45:19,091     Using cached https://www.piwheels.org/simple/setuptools-scm/setuptools_scm-9.2.1-py3-none-any.whl (62 kB)
2025-10-16T21:45:19,322   Collecting wheel
2025-10-16T21:45:19,347     Using cached https://www.piwheels.org/simple/wheel/wheel-0.45.1-py3-none-any.whl (72 kB)
2025-10-16T21:45:19,543   Collecting packaging>=20
2025-10-16T21:45:19,560     Using cached https://www.piwheels.org/simple/packaging/packaging-25.0-py3-none-any.whl (66 kB)
2025-10-16T21:45:22,638   Installing collected packages: wheel, setuptools, packaging, setuptools-scm
2025-10-16T21:45:22,884     Creating /tmp/pip-build-env-0kxzgnu9/overlay/local/bin
2025-10-16T21:45:22,886     changing mode of /tmp/pip-build-env-0kxzgnu9/overlay/local/bin/wheel to 755
2025-10-16T21:45:26,944     changing mode of /tmp/pip-build-env-0kxzgnu9/overlay/local/bin/setuptools-scm to 755
2025-10-16T21:45:26,974   Successfully installed packaging-25.0 setuptools-80.9.0 setuptools-scm-9.2.1 wheel-0.45.1
2025-10-16T21:45:27,265   Installing build dependencies: finished with status 'done'
2025-10-16T21:45:27,272   Getting requirements to build wheel: started
2025-10-16T21:45:27,273   Running command Getting requirements to build wheel
2025-10-16T21:45:27,903   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools_scm/_integration/deprecation.py:7: UserWarning: pyproject.toml: at [tool.setuptools.dynamic]
2025-10-16T21:45:27,904   version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set
2025-10-16T21:45:27,904   When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.
2025-10-16T21:45:27,905   Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.
2025-10-16T21:45:27,905     warnings.warn(
2025-10-16T21:45:28,083   running egg_info
2025-10-16T21:45:28,091   writing inferno_torch.egg-info/PKG-INFO
2025-10-16T21:45:28,104   writing dependency_links to inferno_torch.egg-info/dependency_links.txt
2025-10-16T21:45:28,113   writing requirements to inferno_torch.egg-info/requires.txt
2025-10-16T21:45:28,114   writing top-level names to inferno_torch.egg-info/top_level.txt
2025-10-16T21:45:28,163   listing git files failed - pretending there aren't any
2025-10-16T21:45:28,169   reading manifest file 'inferno_torch.egg-info/SOURCES.txt'
2025-10-16T21:45:28,195   adding license file 'LICENSE'
2025-10-16T21:45:28,202   writing manifest file 'inferno_torch.egg-info/SOURCES.txt'
2025-10-16T21:45:28,304   Getting requirements to build wheel: finished with status 'done'
2025-10-16T21:45:28,308   Created temporary directory: /tmp/pip-modern-metadata-195yom5_
2025-10-16T21:45:28,310   Preparing metadata (pyproject.toml): started
2025-10-16T21:45:28,311   Running command Preparing metadata (pyproject.toml)
2025-10-16T21:45:28,887   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools_scm/_integration/deprecation.py:7: UserWarning: pyproject.toml: at [tool.setuptools.dynamic]
2025-10-16T21:45:28,887   version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set
2025-10-16T21:45:28,888   When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.
2025-10-16T21:45:28,889   Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.
2025-10-16T21:45:28,889     warnings.warn(
2025-10-16T21:45:29,054   running dist_info
2025-10-16T21:45:29,069   creating /tmp/pip-modern-metadata-195yom5_/inferno_torch.egg-info
2025-10-16T21:45:29,070   writing /tmp/pip-modern-metadata-195yom5_/inferno_torch.egg-info/PKG-INFO
2025-10-16T21:45:29,084   writing dependency_links to /tmp/pip-modern-metadata-195yom5_/inferno_torch.egg-info/dependency_links.txt
2025-10-16T21:45:29,092   writing requirements to /tmp/pip-modern-metadata-195yom5_/inferno_torch.egg-info/requires.txt
2025-10-16T21:45:29,093   writing top-level names to /tmp/pip-modern-metadata-195yom5_/inferno_torch.egg-info/top_level.txt
2025-10-16T21:45:29,095   writing manifest file '/tmp/pip-modern-metadata-195yom5_/inferno_torch.egg-info/SOURCES.txt'
2025-10-16T21:45:29,140   listing git files failed - pretending there aren't any
2025-10-16T21:45:29,144   reading manifest file '/tmp/pip-modern-metadata-195yom5_/inferno_torch.egg-info/SOURCES.txt'
2025-10-16T21:45:29,147   adding license file 'LICENSE'
2025-10-16T21:45:29,150   writing manifest file '/tmp/pip-modern-metadata-195yom5_/inferno_torch.egg-info/SOURCES.txt'
2025-10-16T21:45:29,151   creating '/tmp/pip-modern-metadata-195yom5_/inferno_torch-0.0.6.dist-info'
2025-10-16T21:45:29,280   Preparing metadata (pyproject.toml): finished with status 'done'
2025-10-16T21:45:29,285   Source in /tmp/pip-wheel-9gl0ll77/inferno-torch_19cc65742c2e417ab7fd7f09cfffe0f3 has version 0.0.6, which satisfies requirement inferno-torch==0.0.6 from https://files.pythonhosted.org/packages/11/b8/d618b437c79eee753dbb91206c9af7f616f47a673a1273e5cea83e7258a5/inferno_torch-0.0.6.tar.gz
2025-10-16T21:45:29,286   Removed inferno-torch==0.0.6 from https://files.pythonhosted.org/packages/11/b8/d618b437c79eee753dbb91206c9af7f616f47a673a1273e5cea83e7258a5/inferno_torch-0.0.6.tar.gz from build tracker '/tmp/pip-build-tracker-soet21sd'
2025-10-16T21:45:29,291 Created temporary directory: /tmp/pip-unpack-vxchtkix
2025-10-16T21:45:29,292 Building wheels for collected packages: inferno-torch
2025-10-16T21:45:29,296   Created temporary directory: /tmp/pip-wheel-myk50hb3
2025-10-16T21:45:29,297   Destination directory: /tmp/pip-wheel-myk50hb3
2025-10-16T21:45:29,299   Building wheel for inferno-torch (pyproject.toml): started
2025-10-16T21:45:29,300   Running command Building wheel for inferno-torch (pyproject.toml)
2025-10-16T21:45:29,860   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools_scm/_integration/deprecation.py:7: UserWarning: pyproject.toml: at [tool.setuptools.dynamic]
2025-10-16T21:45:29,860   version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set
2025-10-16T21:45:29,861   When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.
2025-10-16T21:45:29,862   Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.
2025-10-16T21:45:29,862     warnings.warn(
2025-10-16T21:45:30,009   running bdist_wheel
2025-10-16T21:45:30,035   running build
2025-10-16T21:45:30,036   running build_py
2025-10-16T21:45:30,044   creating build/lib/inferno
2025-10-16T21:45:30,046   copying inferno/__init__.py -> build/lib/inferno
2025-10-16T21:45:30,049   copying inferno/_version.py -> build/lib/inferno
2025-10-16T21:45:30,050   running egg_info
2025-10-16T21:45:30,064   writing inferno_torch.egg-info/PKG-INFO
2025-10-16T21:45:30,077   writing dependency_links to inferno_torch.egg-info/dependency_links.txt
2025-10-16T21:45:30,085   writing requirements to inferno_torch.egg-info/requires.txt
2025-10-16T21:45:30,086   writing top-level names to inferno_torch.egg-info/top_level.txt
2025-10-16T21:45:30,119   listing git files failed - pretending there aren't any
2025-10-16T21:45:30,123   reading manifest file 'inferno_torch.egg-info/SOURCES.txt'
2025-10-16T21:45:30,131   adding license file 'LICENSE'
2025-10-16T21:45:30,137   writing manifest file 'inferno_torch.egg-info/SOURCES.txt'
2025-10-16T21:45:30,141   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.bnn' is absent from the `packages` configuration.
2025-10-16T21:45:30,142   !!

2025-10-16T21:45:30,143           ********************************************************************************
2025-10-16T21:45:30,144           ############################
2025-10-16T21:45:30,144           # Package would be ignored #
2025-10-16T21:45:30,145           ############################
2025-10-16T21:45:30,146           Python recognizes 'inferno.bnn' as an importable package[^1],
2025-10-16T21:45:30,146           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,147           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,148           package, please make sure that 'inferno.bnn' is explicitly added
2025-10-16T21:45:30,149           to the `packages` configuration field.

2025-10-16T21:45:30,150           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,150           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,151           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,152           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,153           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,153           If you don't want 'inferno.bnn' to be distributed and are
2025-10-16T21:45:30,154           already explicitly excluding 'inferno.bnn' via
2025-10-16T21:45:30,154           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,155           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,155           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,156           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,157           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,161   !!
2025-10-16T21:45:30,162     check.warn(importable)
2025-10-16T21:45:30,162   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.bnn.modules' is absent from the `packages` configuration.
2025-10-16T21:45:30,163   !!

2025-10-16T21:45:30,164           ********************************************************************************
2025-10-16T21:45:30,164           ############################
2025-10-16T21:45:30,165           # Package would be ignored #
2025-10-16T21:45:30,165           ############################
2025-10-16T21:45:30,166           Python recognizes 'inferno.bnn.modules' as an importable package[^1],
2025-10-16T21:45:30,166           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,168           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,168           package, please make sure that 'inferno.bnn.modules' is explicitly added
2025-10-16T21:45:30,169           to the `packages` configuration field.

2025-10-16T21:45:30,170           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,171           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,171           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,172           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,174           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,175           If you don't want 'inferno.bnn.modules' to be distributed and are
2025-10-16T21:45:30,175           already explicitly excluding 'inferno.bnn.modules' via
2025-10-16T21:45:30,176           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,176           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,177           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,178           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,179           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,183   !!
2025-10-16T21:45:30,184     check.warn(importable)
2025-10-16T21:45:30,184   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.bnn.modules.containers' is absent from the `packages` configuration.
2025-10-16T21:45:30,184   !!

2025-10-16T21:45:30,185           ********************************************************************************
2025-10-16T21:45:30,186           ############################
2025-10-16T21:45:30,186           # Package would be ignored #
2025-10-16T21:45:30,187           ############################
2025-10-16T21:45:30,187           Python recognizes 'inferno.bnn.modules.containers' as an importable package[^1],
2025-10-16T21:45:30,188           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,189           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,189           package, please make sure that 'inferno.bnn.modules.containers' is explicitly added
2025-10-16T21:45:30,189           to the `packages` configuration field.

2025-10-16T21:45:30,190           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,191           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,191           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,192           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,193           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,194           If you don't want 'inferno.bnn.modules.containers' to be distributed and are
2025-10-16T21:45:30,195           already explicitly excluding 'inferno.bnn.modules.containers' via
2025-10-16T21:45:30,195           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,196           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,196           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,197           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,198           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,203   !!
2025-10-16T21:45:30,203     check.warn(importable)
2025-10-16T21:45:30,204   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.bnn.params' is absent from the `packages` configuration.
2025-10-16T21:45:30,205   !!

2025-10-16T21:45:30,206           ********************************************************************************
2025-10-16T21:45:30,206           ############################
2025-10-16T21:45:30,207           # Package would be ignored #
2025-10-16T21:45:30,207           ############################
2025-10-16T21:45:30,208           Python recognizes 'inferno.bnn.params' as an importable package[^1],
2025-10-16T21:45:30,209           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,210           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,210           package, please make sure that 'inferno.bnn.params' is explicitly added
2025-10-16T21:45:30,210           to the `packages` configuration field.

2025-10-16T21:45:30,211           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,212           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,212           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,213           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,214           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,215           If you don't want 'inferno.bnn.params' to be distributed and are
2025-10-16T21:45:30,215           already explicitly excluding 'inferno.bnn.params' via
2025-10-16T21:45:30,215           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,216           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,216           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,217           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,218           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,223   !!
2025-10-16T21:45:30,224     check.warn(importable)
2025-10-16T21:45:30,224   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.bnn.params.covariances' is absent from the `packages` configuration.
2025-10-16T21:45:30,225   !!

2025-10-16T21:45:30,226           ********************************************************************************
2025-10-16T21:45:30,226           ############################
2025-10-16T21:45:30,227           # Package would be ignored #
2025-10-16T21:45:30,227           ############################
2025-10-16T21:45:30,228           Python recognizes 'inferno.bnn.params.covariances' as an importable package[^1],
2025-10-16T21:45:30,228           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,229           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,230           package, please make sure that 'inferno.bnn.params.covariances' is explicitly added
2025-10-16T21:45:30,230           to the `packages` configuration field.

2025-10-16T21:45:30,232           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,232           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,232           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,233           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,235           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,236           If you don't want 'inferno.bnn.params.covariances' to be distributed and are
2025-10-16T21:45:30,236           already explicitly excluding 'inferno.bnn.params.covariances' via
2025-10-16T21:45:30,237           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,238           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,238           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,239           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,240           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,244   !!
2025-10-16T21:45:30,245     check.warn(importable)
2025-10-16T21:45:30,245   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.bnn.params.parametrizations' is absent from the `packages` configuration.
2025-10-16T21:45:30,246   !!

2025-10-16T21:45:30,247           ********************************************************************************
2025-10-16T21:45:30,247           ############################
2025-10-16T21:45:30,247           # Package would be ignored #
2025-10-16T21:45:30,248           ############################
2025-10-16T21:45:30,248           Python recognizes 'inferno.bnn.params.parametrizations' as an importable package[^1],
2025-10-16T21:45:30,249           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,250           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,250           package, please make sure that 'inferno.bnn.params.parametrizations' is explicitly added
2025-10-16T21:45:30,251           to the `packages` configuration field.

2025-10-16T21:45:30,252           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,252           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,253           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,254           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,255           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,256           If you don't want 'inferno.bnn.params.parametrizations' to be distributed and are
2025-10-16T21:45:30,257           already explicitly excluding 'inferno.bnn.params.parametrizations' via
2025-10-16T21:45:30,257           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,258           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,258           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,259           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,260           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,265   !!
2025-10-16T21:45:30,266     check.warn(importable)
2025-10-16T21:45:30,266   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.datasets' is absent from the `packages` configuration.
2025-10-16T21:45:30,267   !!

2025-10-16T21:45:30,268           ********************************************************************************
2025-10-16T21:45:30,268           ############################
2025-10-16T21:45:30,269           # Package would be ignored #
2025-10-16T21:45:30,269           ############################
2025-10-16T21:45:30,269           Python recognizes 'inferno.datasets' as an importable package[^1],
2025-10-16T21:45:30,270           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,271           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,271           package, please make sure that 'inferno.datasets' is explicitly added
2025-10-16T21:45:30,271           to the `packages` configuration field.

2025-10-16T21:45:30,272           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,273           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,273           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,274           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,275           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,276           If you don't want 'inferno.datasets' to be distributed and are
2025-10-16T21:45:30,277           already explicitly excluding 'inferno.datasets' via
2025-10-16T21:45:30,277           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,278           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,278           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,279           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,280           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,285   !!
2025-10-16T21:45:30,285     check.warn(importable)
2025-10-16T21:45:30,286   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.datasets.image' is absent from the `packages` configuration.
2025-10-16T21:45:30,286   !!

2025-10-16T21:45:30,287           ********************************************************************************
2025-10-16T21:45:30,288           ############################
2025-10-16T21:45:30,288           # Package would be ignored #
2025-10-16T21:45:30,289           ############################
2025-10-16T21:45:30,289           Python recognizes 'inferno.datasets.image' as an importable package[^1],
2025-10-16T21:45:30,290           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,291           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,292           package, please make sure that 'inferno.datasets.image' is explicitly added
2025-10-16T21:45:30,292           to the `packages` configuration field.

2025-10-16T21:45:30,293           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,294           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,294           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,296           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,297           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,297           If you don't want 'inferno.datasets.image' to be distributed and are
2025-10-16T21:45:30,298           already explicitly excluding 'inferno.datasets.image' via
2025-10-16T21:45:30,298           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,299           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,299           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,300           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,301           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,306   !!
2025-10-16T21:45:30,306     check.warn(importable)
2025-10-16T21:45:30,307   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.datasets.tabular' is absent from the `packages` configuration.
2025-10-16T21:45:30,307   !!

2025-10-16T21:45:30,308           ********************************************************************************
2025-10-16T21:45:30,309           ############################
2025-10-16T21:45:30,309           # Package would be ignored #
2025-10-16T21:45:30,310           ############################
2025-10-16T21:45:30,311           Python recognizes 'inferno.datasets.tabular' as an importable package[^1],
2025-10-16T21:45:30,311           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,312           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,313           package, please make sure that 'inferno.datasets.tabular' is explicitly added
2025-10-16T21:45:30,314           to the `packages` configuration field.

2025-10-16T21:45:30,315           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,316           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,316           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,318           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,319           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,320           If you don't want 'inferno.datasets.tabular' to be distributed and are
2025-10-16T21:45:30,320           already explicitly excluding 'inferno.datasets.tabular' via
2025-10-16T21:45:30,321           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,321           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,322           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,323           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,324           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,330   !!
2025-10-16T21:45:30,330     check.warn(importable)
2025-10-16T21:45:30,330   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.datasets.text' is absent from the `packages` configuration.
2025-10-16T21:45:30,331   !!

2025-10-16T21:45:30,332           ********************************************************************************
2025-10-16T21:45:30,332           ############################
2025-10-16T21:45:30,332           # Package would be ignored #
2025-10-16T21:45:30,333           ############################
2025-10-16T21:45:30,333           Python recognizes 'inferno.datasets.text' as an importable package[^1],
2025-10-16T21:45:30,334           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,334           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,335           package, please make sure that 'inferno.datasets.text' is explicitly added
2025-10-16T21:45:30,335           to the `packages` configuration field.

2025-10-16T21:45:30,336           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,337           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,337           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,338           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,339           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,341           If you don't want 'inferno.datasets.text' to be distributed and are
2025-10-16T21:45:30,341           already explicitly excluding 'inferno.datasets.text' via
2025-10-16T21:45:30,342           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,342           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,343           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,344           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,346           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,351   !!
2025-10-16T21:45:30,351     check.warn(importable)
2025-10-16T21:45:30,352   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.loss_fns' is absent from the `packages` configuration.
2025-10-16T21:45:30,353   !!

2025-10-16T21:45:30,354           ********************************************************************************
2025-10-16T21:45:30,354           ############################
2025-10-16T21:45:30,355           # Package would be ignored #
2025-10-16T21:45:30,355           ############################
2025-10-16T21:45:30,356           Python recognizes 'inferno.loss_fns' as an importable package[^1],
2025-10-16T21:45:30,357           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,358           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,359           package, please make sure that 'inferno.loss_fns' is explicitly added
2025-10-16T21:45:30,360           to the `packages` configuration field.

2025-10-16T21:45:30,360           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,361           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,361           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,362           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,363           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,364           If you don't want 'inferno.loss_fns' to be distributed and are
2025-10-16T21:45:30,364           already explicitly excluding 'inferno.loss_fns' via
2025-10-16T21:45:30,365           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,365           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,366           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,367           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,368           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,372   !!
2025-10-16T21:45:30,373     check.warn(importable)
2025-10-16T21:45:30,373   /tmp/pip-build-env-0kxzgnu9/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'inferno.models' is absent from the `packages` configuration.
2025-10-16T21:45:30,374   !!

2025-10-16T21:45:30,375           ********************************************************************************
2025-10-16T21:45:30,375           ############################
2025-10-16T21:45:30,376           # Package would be ignored #
2025-10-16T21:45:30,376           ############################
2025-10-16T21:45:30,377           Python recognizes 'inferno.models' as an importable package[^1],
2025-10-16T21:45:30,377           but it is absent from setuptools' `packages` configuration.

2025-10-16T21:45:30,378           This leads to an ambiguous overall configuration. If you want to distribute this
2025-10-16T21:45:30,379           package, please make sure that 'inferno.models' is explicitly added
2025-10-16T21:45:30,379           to the `packages` configuration field.

2025-10-16T21:45:30,380           Alternatively, you can also rely on setuptools' discovery methods
2025-10-16T21:45:30,381           (for example by using `find_namespace_packages(...)`/`find_namespace:`
2025-10-16T21:45:30,381           instead of `find_packages(...)`/`find:`).

2025-10-16T21:45:30,382           You can read more about "package discovery" on setuptools documentation page:

2025-10-16T21:45:30,383           - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

2025-10-16T21:45:30,384           If you don't want 'inferno.models' to be distributed and are
2025-10-16T21:45:30,385           already explicitly excluding 'inferno.models' via
2025-10-16T21:45:30,385           `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
2025-10-16T21:45:30,386           you can try to use `exclude_package_data`, or `include-package-data=False` in
2025-10-16T21:45:30,386           combination with a more fine grained `package-data` configuration.

2025-10-16T21:45:30,388           You can read more about "package data files" on setuptools documentation page:

2025-10-16T21:45:30,389           - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

2025-10-16T21:45:30,392   !!
2025-10-16T21:45:30,393     check.warn(importable)
2025-10-16T21:45:30,393   copying inferno/.gitignore -> build/lib/inferno
2025-10-16T21:45:30,393   creating build/lib/inferno/bnn
2025-10-16T21:45:30,394   copying inferno/bnn/__init__.py -> build/lib/inferno/bnn
2025-10-16T21:45:30,394   copying inferno/bnn/temperature_scaler.py -> build/lib/inferno/bnn
2025-10-16T21:45:30,395   creating build/lib/inferno/bnn/modules
2025-10-16T21:45:30,395   copying inferno/bnn/modules/__init__.py -> build/lib/inferno/bnn/modules
2025-10-16T21:45:30,395   copying inferno/bnn/modules/bnn_mixin.py -> build/lib/inferno/bnn/modules
2025-10-16T21:45:30,396   copying inferno/bnn/modules/conv.py -> build/lib/inferno/bnn/modules
2025-10-16T21:45:30,397   copying inferno/bnn/modules/linear.py -> build/lib/inferno/bnn/modules
2025-10-16T21:45:30,397   creating build/lib/inferno/bnn/modules/containers
2025-10-16T21:45:30,398   copying inferno/bnn/modules/containers/__init__.py -> build/lib/inferno/bnn/modules/containers
2025-10-16T21:45:30,398   copying inferno/bnn/modules/containers/sequential.py -> build/lib/inferno/bnn/modules/containers
2025-10-16T21:45:30,399   creating build/lib/inferno/bnn/params
2025-10-16T21:45:30,399   copying inferno/bnn/params/__init__.py -> build/lib/inferno/bnn/params
2025-10-16T21:45:30,400   copying inferno/bnn/params/gaussian_parameter.py -> build/lib/inferno/bnn/params
2025-10-16T21:45:30,400   copying inferno/bnn/params/parameter.py -> build/lib/inferno/bnn/params
2025-10-16T21:45:30,401   creating build/lib/inferno/bnn/params/covariances
2025-10-16T21:45:30,401   copying inferno/bnn/params/covariances/__init__.py -> build/lib/inferno/bnn/params/covariances
2025-10-16T21:45:30,402   copying inferno/bnn/params/covariances/diagonal.py -> build/lib/inferno/bnn/params/covariances
2025-10-16T21:45:30,402   copying inferno/bnn/params/covariances/factorized.py -> build/lib/inferno/bnn/params/covariances
2025-10-16T21:45:30,403   copying inferno/bnn/params/covariances/kronecker.py -> build/lib/inferno/bnn/params/covariances
2025-10-16T21:45:30,403   copying inferno/bnn/params/covariances/low_rank.py -> build/lib/inferno/bnn/params/covariances
2025-10-16T21:45:30,404   creating build/lib/inferno/bnn/params/parametrizations
2025-10-16T21:45:30,405   copying inferno/bnn/params/parametrizations/__init__.py -> build/lib/inferno/bnn/params/parametrizations
2025-10-16T21:45:30,405   copying inferno/bnn/params/parametrizations/maximal_update.py -> build/lib/inferno/bnn/params/parametrizations
2025-10-16T21:45:30,406   copying inferno/bnn/params/parametrizations/neural_tangent.py -> build/lib/inferno/bnn/params/parametrizations
2025-10-16T21:45:30,406   copying inferno/bnn/params/parametrizations/parametrization.py -> build/lib/inferno/bnn/params/parametrizations
2025-10-16T21:45:30,407   copying inferno/bnn/params/parametrizations/standard.py -> build/lib/inferno/bnn/params/parametrizations
2025-10-16T21:45:30,407   creating build/lib/inferno/datasets
2025-10-16T21:45:30,408   copying inferno/datasets/__init__.py -> build/lib/inferno/datasets
2025-10-16T21:45:30,408   copying inferno/datasets/regression_dataset.py -> build/lib/inferno/datasets
2025-10-16T21:45:30,409   creating build/lib/inferno/datasets/image
2025-10-16T21:45:30,410   copying inferno/datasets/image/__init__.py -> build/lib/inferno/datasets/image
2025-10-16T21:45:30,411   copying inferno/datasets/image/cifar.py -> build/lib/inferno/datasets/image
2025-10-16T21:45:30,412   copying inferno/datasets/image/fashion_mnist.py -> build/lib/inferno/datasets/image
2025-10-16T21:45:30,412   copying inferno/datasets/image/mnist.py -> build/lib/inferno/datasets/image
2025-10-16T21:45:30,413   copying inferno/datasets/image/tiny_imagenet.py -> build/lib/inferno/datasets/image
2025-10-16T21:45:30,413   creating build/lib/inferno/datasets/tabular
2025-10-16T21:45:30,414   copying inferno/datasets/tabular/__init__.py -> build/lib/inferno/datasets/tabular
2025-10-16T21:45:30,414   copying inferno/datasets/tabular/concrete_compressive_strength.py -> build/lib/inferno/datasets/tabular
2025-10-16T21:45:30,414   copying inferno/datasets/tabular/parkinsons_telemonitoring.py -> build/lib/inferno/datasets/tabular
2025-10-16T21:45:30,415   copying inferno/datasets/tabular/protein_structure.py -> build/lib/inferno/datasets/tabular
2025-10-16T21:45:30,415   copying inferno/datasets/tabular/road_network.py -> build/lib/inferno/datasets/tabular
2025-10-16T21:45:30,416   copying inferno/datasets/tabular/wine_quality.py -> build/lib/inferno/datasets/tabular
2025-10-16T21:45:30,416   creating build/lib/inferno/datasets/text
2025-10-16T21:45:30,417   copying inferno/datasets/text/__init__.py -> build/lib/inferno/datasets/text
2025-10-16T21:45:30,417   creating build/lib/inferno/loss_fns
2025-10-16T21:45:30,418   copying inferno/loss_fns/__init__.py -> build/lib/inferno/loss_fns
2025-10-16T21:45:30,418   copying inferno/loss_fns/variational_free_energy.py -> build/lib/inferno/loss_fns
2025-10-16T21:45:30,418   copying inferno/loss_fns/wrapped_torch_loss_fns.py -> build/lib/inferno/loss_fns
2025-10-16T21:45:30,419   creating build/lib/inferno/models
2025-10-16T21:45:30,419   copying inferno/models/__init__.py -> build/lib/inferno/models
2025-10-16T21:45:30,420   copying inferno/models/ensemble.py -> build/lib/inferno/models
2025-10-16T21:45:30,420   copying inferno/models/lenet5.py -> build/lib/inferno/models
2025-10-16T21:45:30,421   copying inferno/models/mlp.py -> build/lib/inferno/models
2025-10-16T21:45:30,421   copying inferno/models/resnet.py -> build/lib/inferno/models
2025-10-16T21:45:30,422   installing to build/bdist.linux-armv7l/wheel
2025-10-16T21:45:30,423   running install
2025-10-16T21:45:30,423   running install_lib
2025-10-16T21:45:30,424   creating build/bdist.linux-armv7l/wheel
2025-10-16T21:45:30,424   creating build/bdist.linux-armv7l/wheel/inferno
2025-10-16T21:45:30,425   creating build/bdist.linux-armv7l/wheel/inferno/models
2025-10-16T21:45:30,425   copying build/lib/inferno/models/mlp.py -> build/bdist.linux-armv7l/wheel/./inferno/models
2025-10-16T21:45:30,426   copying build/lib/inferno/models/resnet.py -> build/bdist.linux-armv7l/wheel/./inferno/models
2025-10-16T21:45:30,426   copying build/lib/inferno/models/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/models
2025-10-16T21:45:30,427   copying build/lib/inferno/models/lenet5.py -> build/bdist.linux-armv7l/wheel/./inferno/models
2025-10-16T21:45:30,428   copying build/lib/inferno/models/ensemble.py -> build/bdist.linux-armv7l/wheel/./inferno/models
2025-10-16T21:45:30,428   creating build/bdist.linux-armv7l/wheel/inferno/loss_fns
2025-10-16T21:45:30,429   copying build/lib/inferno/loss_fns/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/loss_fns
2025-10-16T21:45:30,429   copying build/lib/inferno/loss_fns/variational_free_energy.py -> build/bdist.linux-armv7l/wheel/./inferno/loss_fns
2025-10-16T21:45:30,430   copying build/lib/inferno/loss_fns/wrapped_torch_loss_fns.py -> build/bdist.linux-armv7l/wheel/./inferno/loss_fns
2025-10-16T21:45:30,430   copying build/lib/inferno/.gitignore -> build/bdist.linux-armv7l/wheel/./inferno
2025-10-16T21:45:30,431   copying build/lib/inferno/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno
2025-10-16T21:45:30,431   copying build/lib/inferno/_version.py -> build/bdist.linux-armv7l/wheel/./inferno
2025-10-16T21:45:30,432   creating build/bdist.linux-armv7l/wheel/inferno/datasets
2025-10-16T21:45:30,432   copying build/lib/inferno/datasets/regression_dataset.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets
2025-10-16T21:45:30,433   creating build/bdist.linux-armv7l/wheel/inferno/datasets/image
2025-10-16T21:45:30,434   copying build/lib/inferno/datasets/image/cifar.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/image
2025-10-16T21:45:30,434   copying build/lib/inferno/datasets/image/fashion_mnist.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/image
2025-10-16T21:45:30,435   copying build/lib/inferno/datasets/image/tiny_imagenet.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/image
2025-10-16T21:45:30,435   copying build/lib/inferno/datasets/image/mnist.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/image
2025-10-16T21:45:30,435   copying build/lib/inferno/datasets/image/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/image
2025-10-16T21:45:30,436   copying build/lib/inferno/datasets/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets
2025-10-16T21:45:30,436   creating build/bdist.linux-armv7l/wheel/inferno/datasets/text
2025-10-16T21:45:30,437   copying build/lib/inferno/datasets/text/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/text
2025-10-16T21:45:30,437   creating build/bdist.linux-armv7l/wheel/inferno/datasets/tabular
2025-10-16T21:45:30,438   copying build/lib/inferno/datasets/tabular/road_network.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/tabular
2025-10-16T21:45:30,438   copying build/lib/inferno/datasets/tabular/wine_quality.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/tabular
2025-10-16T21:45:30,439   copying build/lib/inferno/datasets/tabular/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/tabular
2025-10-16T21:45:30,439   copying build/lib/inferno/datasets/tabular/protein_structure.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/tabular
2025-10-16T21:45:30,440   copying build/lib/inferno/datasets/tabular/concrete_compressive_strength.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/tabular
2025-10-16T21:45:30,440   copying build/lib/inferno/datasets/tabular/parkinsons_telemonitoring.py -> build/bdist.linux-armv7l/wheel/./inferno/datasets/tabular
2025-10-16T21:45:30,441   creating build/bdist.linux-armv7l/wheel/inferno/bnn
2025-10-16T21:45:30,441   creating build/bdist.linux-armv7l/wheel/inferno/bnn/params
2025-10-16T21:45:30,442   copying build/lib/inferno/bnn/params/parameter.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params
2025-10-16T21:45:30,444   copying build/lib/inferno/bnn/params/gaussian_parameter.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params
2025-10-16T21:45:30,446   copying build/lib/inferno/bnn/params/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params
2025-10-16T21:45:30,449   creating build/bdist.linux-armv7l/wheel/inferno/bnn/params/covariances
2025-10-16T21:45:30,450   copying build/lib/inferno/bnn/params/covariances/low_rank.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/covariances
2025-10-16T21:45:30,452   copying build/lib/inferno/bnn/params/covariances/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/covariances
2025-10-16T21:45:30,453   copying build/lib/inferno/bnn/params/covariances/factorized.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/covariances
2025-10-16T21:45:30,456   copying build/lib/inferno/bnn/params/covariances/diagonal.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/covariances
2025-10-16T21:45:30,458   copying build/lib/inferno/bnn/params/covariances/kronecker.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/covariances
2025-10-16T21:45:30,461   creating build/bdist.linux-armv7l/wheel/inferno/bnn/params/parametrizations
2025-10-16T21:45:30,462   copying build/lib/inferno/bnn/params/parametrizations/parametrization.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/parametrizations
2025-10-16T21:45:30,464   copying build/lib/inferno/bnn/params/parametrizations/maximal_update.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/parametrizations
2025-10-16T21:45:30,466   copying build/lib/inferno/bnn/params/parametrizations/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/parametrizations
2025-10-16T21:45:30,468   copying build/lib/inferno/bnn/params/parametrizations/neural_tangent.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/parametrizations
2025-10-16T21:45:30,470   copying build/lib/inferno/bnn/params/parametrizations/standard.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/params/parametrizations
2025-10-16T21:45:30,473   creating build/bdist.linux-armv7l/wheel/inferno/bnn/modules
2025-10-16T21:45:30,474   creating build/bdist.linux-armv7l/wheel/inferno/bnn/modules/containers
2025-10-16T21:45:30,475   copying build/lib/inferno/bnn/modules/containers/sequential.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/modules/containers
2025-10-16T21:45:30,478   copying build/lib/inferno/bnn/modules/containers/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/modules/containers
2025-10-16T21:45:30,479   copying build/lib/inferno/bnn/modules/linear.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/modules
2025-10-16T21:45:30,482   copying build/lib/inferno/bnn/modules/bnn_mixin.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/modules
2025-10-16T21:45:30,484   copying build/lib/inferno/bnn/modules/conv.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/modules
2025-10-16T21:45:30,487   copying build/lib/inferno/bnn/modules/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn/modules
2025-10-16T21:45:30,489   copying build/lib/inferno/bnn/__init__.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn
2025-10-16T21:45:30,491   copying build/lib/inferno/bnn/temperature_scaler.py -> build/bdist.linux-armv7l/wheel/./inferno/bnn
2025-10-16T21:45:30,492   running install_egg_info
2025-10-16T21:45:30,500   Copying inferno_torch.egg-info to build/bdist.linux-armv7l/wheel/./inferno_torch-0.0.6-py3.11.egg-info
2025-10-16T21:45:30,512   running install_scripts
2025-10-16T21:45:30,524   creating build/bdist.linux-armv7l/wheel/inferno_torch-0.0.6.dist-info/WHEEL
2025-10-16T21:45:30,527   creating '/tmp/pip-wheel-myk50hb3/.tmp-7v_1469h/inferno_torch-0.0.6-py3-none-any.whl' and adding 'build/bdist.linux-armv7l/wheel' to it
2025-10-16T21:45:30,529   adding 'inferno/.gitignore'
2025-10-16T21:45:30,530   adding 'inferno/__init__.py'
2025-10-16T21:45:30,532   adding 'inferno/_version.py'
2025-10-16T21:45:30,533   adding 'inferno/bnn/__init__.py'
2025-10-16T21:45:30,535   adding 'inferno/bnn/temperature_scaler.py'
2025-10-16T21:45:30,537   adding 'inferno/bnn/modules/__init__.py'
2025-10-16T21:45:30,539   adding 'inferno/bnn/modules/bnn_mixin.py'
2025-10-16T21:45:30,541   adding 'inferno/bnn/modules/conv.py'
2025-10-16T21:45:30,543   adding 'inferno/bnn/modules/linear.py'
2025-10-16T21:45:30,546   adding 'inferno/bnn/modules/containers/__init__.py'
2025-10-16T21:45:30,547   adding 'inferno/bnn/modules/containers/sequential.py'
2025-10-16T21:45:30,549   adding 'inferno/bnn/params/__init__.py'
2025-10-16T21:45:30,551   adding 'inferno/bnn/params/gaussian_parameter.py'
2025-10-16T21:45:30,552   adding 'inferno/bnn/params/parameter.py'
2025-10-16T21:45:30,554   adding 'inferno/bnn/params/covariances/__init__.py'
2025-10-16T21:45:30,555   adding 'inferno/bnn/params/covariances/diagonal.py'
2025-10-16T21:45:30,557   adding 'inferno/bnn/params/covariances/factorized.py'
2025-10-16T21:45:30,558   adding 'inferno/bnn/params/covariances/kronecker.py'
2025-10-16T21:45:30,560   adding 'inferno/bnn/params/covariances/low_rank.py'
2025-10-16T21:45:30,562   adding 'inferno/bnn/params/parametrizations/__init__.py'
2025-10-16T21:45:30,563   adding 'inferno/bnn/params/parametrizations/maximal_update.py'
2025-10-16T21:45:30,564   adding 'inferno/bnn/params/parametrizations/neural_tangent.py'
2025-10-16T21:45:30,566   adding 'inferno/bnn/params/parametrizations/parametrization.py'
2025-10-16T21:45:30,567   adding 'inferno/bnn/params/parametrizations/standard.py'
2025-10-16T21:45:30,569   adding 'inferno/datasets/__init__.py'
2025-10-16T21:45:30,571   adding 'inferno/datasets/regression_dataset.py'
2025-10-16T21:45:30,572   adding 'inferno/datasets/image/__init__.py'
2025-10-16T21:45:30,574   adding 'inferno/datasets/image/cifar.py'
2025-10-16T21:45:30,575   adding 'inferno/datasets/image/fashion_mnist.py'
2025-10-16T21:45:30,577   adding 'inferno/datasets/image/mnist.py'
2025-10-16T21:45:30,578   adding 'inferno/datasets/image/tiny_imagenet.py'
2025-10-16T21:45:30,580   adding 'inferno/datasets/tabular/__init__.py'
2025-10-16T21:45:30,582   adding 'inferno/datasets/tabular/concrete_compressive_strength.py'
2025-10-16T21:45:30,583   adding 'inferno/datasets/tabular/parkinsons_telemonitoring.py'
2025-10-16T21:45:30,584   adding 'inferno/datasets/tabular/protein_structure.py'
2025-10-16T21:45:30,586   adding 'inferno/datasets/tabular/road_network.py'
2025-10-16T21:45:30,587   adding 'inferno/datasets/tabular/wine_quality.py'
2025-10-16T21:45:30,589   adding 'inferno/datasets/text/__init__.py'
2025-10-16T21:45:30,590   adding 'inferno/loss_fns/__init__.py'
2025-10-16T21:45:30,592   adding 'inferno/loss_fns/variational_free_energy.py'
2025-10-16T21:45:30,593   adding 'inferno/loss_fns/wrapped_torch_loss_fns.py'
2025-10-16T21:45:30,595   adding 'inferno/models/__init__.py'
2025-10-16T21:45:30,596   adding 'inferno/models/ensemble.py'
2025-10-16T21:45:30,598   adding 'inferno/models/lenet5.py'
2025-10-16T21:45:30,599   adding 'inferno/models/mlp.py'
2025-10-16T21:45:30,602   adding 'inferno/models/resnet.py'
2025-10-16T21:45:30,605   adding 'inferno_torch-0.0.6.dist-info/licenses/LICENSE'
2025-10-16T21:45:30,606   adding 'inferno_torch-0.0.6.dist-info/METADATA'
2025-10-16T21:45:30,607   adding 'inferno_torch-0.0.6.dist-info/WHEEL'
2025-10-16T21:45:30,608   adding 'inferno_torch-0.0.6.dist-info/top_level.txt'
2025-10-16T21:45:30,609   adding 'inferno_torch-0.0.6.dist-info/RECORD'
2025-10-16T21:45:30,611   removing build/bdist.linux-armv7l/wheel
2025-10-16T21:45:30,733   Building wheel for inferno-torch (pyproject.toml): finished with status 'done'
2025-10-16T21:45:30,739   Created wheel for inferno-torch: filename=inferno_torch-0.0.6-py3-none-any.whl size=58972 sha256=e5e95af083851d1dfd51160ea0981f8a63177d9e092a1ffc8e9bff59cb5f282a
2025-10-16T21:45:30,740   Stored in directory: /tmp/pip-ephem-wheel-cache-1yddkrdr/wheels/a3/e9/3a/c2d490a1b515af074df05f24fd48d36e88188fac983b72f73a
2025-10-16T21:45:30,752 Successfully built inferno-torch
2025-10-16T21:45:30,757 Removed build tracker: '/tmp/pip-build-tracker-soet21sd'