2025-12-16T15:03:46,967 Created temporary directory: /tmp/pip-ephem-wheel-cache-xxobqpop 2025-12-16T15:03:46,969 Created temporary directory: /tmp/pip-build-tracker-yu7v86hm 2025-12-16T15:03:46,969 Initialized build tracking at /tmp/pip-build-tracker-yu7v86hm 2025-12-16T15:03:46,970 Created build tracker: /tmp/pip-build-tracker-yu7v86hm 2025-12-16T15:03:46,970 Entered build tracker: /tmp/pip-build-tracker-yu7v86hm 2025-12-16T15:03:46,971 Created temporary directory: /tmp/pip-wheel-heqq4gmj 2025-12-16T15:03:46,974 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-12-16T15:03:46,976 Created temporary directory: /tmp/pip-ephem-wheel-cache-ay09v5t0 2025-12-16T15:03:46,998 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-12-16T15:03:47,002 2 location(s) to search for versions of seal5: 2025-12-16T15:03:47,002 * https://pypi.org/simple/seal5/ 2025-12-16T15:03:47,002 * https://www.piwheels.org/simple/seal5/ 2025-12-16T15:03:47,003 Fetching project page and analyzing links: https://pypi.org/simple/seal5/ 2025-12-16T15:03:47,004 Getting page https://pypi.org/simple/seal5/ 2025-12-16T15:03:47,005 Found index url https://pypi.org/simple 2025-12-16T15:03:47,217 Fetched page https://pypi.org/simple/seal5/ as application/vnd.pypi.simple.v1+json 2025-12-16T15:03:47,222 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/f8/ae/3ae56a5a2ac729d6f3311105d8d7b1cc9ab6e4a339af6eae6103596f0d86/seal5-0.1.0.dev0-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,222 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/d0/08/f1fb860506eda81695a5029eb9c62527dbe94993334e29ad3ab52f3cc4c9/seal5-0.1.1.dev0-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,223 Found link https://files.pythonhosted.org/packages/f6/32/5093f9d9bade6bd23974f28cd4273badc1775232963333387c2ec4f706a9/seal5-0.1.1.dev0.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.1.1.dev0 2025-12-16T15:03:47,224 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/1d/63/f1f1bef31ff2df37739f70696e10024e0e78522e0afd7bd2e7471e03969f/seal5-0.1.2-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,225 Found link https://files.pythonhosted.org/packages/08/b5/9f567f298377348179dc738c13e1112ea3802fec8eee6f9340f02ab4230a/seal5-0.1.2.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.1.2 2025-12-16T15:03:47,226 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/94/d4/a9b1351d4c3be9bf047399e73bdb194b895090c6bb6f0cca2c933b683da7/seal5-0.1.3-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,227 Found link https://files.pythonhosted.org/packages/e6/3c/9880ee9653d2ccda10caa8cb05c3675b079b9aab5c9857bb7ddda237add7/seal5-0.1.3.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.1.3 2025-12-16T15:03:47,228 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/d3/cb/d5b4c65c3172714979b82ce1f97ece185b072cb00762e474bc2b0cf16e1e/seal5-0.1.4-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,228 Found link https://files.pythonhosted.org/packages/8e/b8/66f18763cd3fc041148d3f1a60d9b34170fac2bb7b554cf28116f40b220d/seal5-0.1.4.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.1.4 2025-12-16T15:03:47,229 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/23/0f/9d8f3d6a198479d5bfeb21a83fbcf5d63d7ce61071fc3e802b486af45357/seal5-0.2.0-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,230 Found link https://files.pythonhosted.org/packages/ab/cf/629d9838515d4a414fac8d5f43c86c197d6f9e9aa9d3c93da98153aeca27/seal5-0.2.0.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.2.0 2025-12-16T15:03:47,231 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/64/2b/e3deec1bcfe91ddf65882dd3a10d13e3b0acff1038116dfa08e2f4551080/seal5-0.3.0-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,232 Found link https://files.pythonhosted.org/packages/1c/67/ac7c5a312aae734e9be027768a6a9789cb36aee36e757afd4e599c52bb27/seal5-0.3.0.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.3.0 2025-12-16T15:03:47,233 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/6b/4f/6e1aad0e6195a1cb2ec9645f32391a9d4186a5b0876b75b1aca45ad243c1/seal5-0.3.1-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,233 Found link https://files.pythonhosted.org/packages/f9/e3/6765c06785c0c68d1f765feaa080c84f9a0bbcb4fa34df08b2dc65249669/seal5-0.3.1.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.3.1 2025-12-16T15:03:47,234 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/7b/6f/05d421bba39e103091b3add52f61e3f293ff3a286d927371edacfef45723/seal5-0.3.2-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.10) 2025-12-16T15:03:47,235 Found link https://files.pythonhosted.org/packages/cb/51/0742f8a29f326e1233bf6a637811be514f1d31fba050e29b8a56f283d7c0/seal5-0.3.2.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.10), version: 0.3.2 2025-12-16T15:03:47,235 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/eb/e6/ac334cf69e88d424a2f5a70bbce88a21909b15de29d138606eea6197487c/seal5-0.3.3-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.10) 2025-12-16T15:03:47,236 Found link https://files.pythonhosted.org/packages/f6/46/ff32bb0db3b7907b3f9735255eedb74c5b9d66db709a69ce05c055a16cde/seal5-0.3.3.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.10), version: 0.3.3 2025-12-16T15:03:47,237 Fetching project page and analyzing links: https://www.piwheels.org/simple/seal5/ 2025-12-16T15:03:47,238 Getting page https://www.piwheels.org/simple/seal5/ 2025-12-16T15:03:47,239 Found index url https://www.piwheels.org/simple 2025-12-16T15:03:47,394 Fetched page https://www.piwheels.org/simple/seal5/ as text/html 2025-12-16T15:03:47,397 Skipping link: No binaries permitted for seal5: https://www.piwheels.org/simple/seal5/seal5-0.3.2-py3-none-any.whl#sha256=ce5406f34e574e238611e81da6d677cc556cda15e189810126da3ad7f2c08821 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.10) 2025-12-16T15:03:47,398 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.3.1-py3-none-any.whl#sha256=8d1d70b0dd7880884070df245db646345a921681816d4de0facfbef840af9a20 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,399 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.3.0-py3-none-any.whl#sha256=3ee5e04472ec4b991048da9c54e9ad3b634797fa191d9d4040d99f388e9ea091 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,399 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.2.0-py3-none-any.whl#sha256=4215666ed62a5b68c7e63923b814182da049bd044230489bf7c7d76fd1f28285 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,400 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.1.4-py3-none-any.whl#sha256=124235386909d38ba252e9bed0b9837b75d2f5f18d977852be818589651e6e6d (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,400 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.1.3-py3-none-any.whl#sha256=3a961dcced5a05f2b43aa4ffdd0912879a06892966dfb1a999bd556a84686967 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,401 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.1.2-py3-none-any.whl#sha256=a4b69393213ff899308d4cd82005a43f055a577f95eba42e7cb39636ddc1144a (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,402 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.1.1.dev0-py3-none-any.whl#sha256=9921841f51a0dfe349f86cc3ee44d6a61648a9abfb16053ec71fb468a1475f28 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-16T15:03:47,402 Skipping link: not a file: https://www.piwheels.org/simple/seal5/ 2025-12-16T15:03:47,403 Skipping link: not a file: https://pypi.org/simple/seal5/ 2025-12-16T15:03:47,422 Given no hashes to check 1 links for project 'seal5': discarding no candidates 2025-12-16T15:03:47,440 Collecting seal5==0.3.3 2025-12-16T15:03:47,442 Created temporary directory: /tmp/pip-unpack-1i7w_ug5 2025-12-16T15:03:47,655 Downloading seal5-0.3.3.tar.gz (354 kB) 2025-12-16T15:03:48,751 Added seal5==0.3.3 from https://files.pythonhosted.org/packages/f6/46/ff32bb0db3b7907b3f9735255eedb74c5b9d66db709a69ce05c055a16cde/seal5-0.3.3.tar.gz to build tracker '/tmp/pip-build-tracker-yu7v86hm' 2025-12-16T15:03:48,757 Created temporary directory: /tmp/pip-build-env-p_o30ioa 2025-12-16T15:03:48,762 Installing build dependencies: started 2025-12-16T15:03:48,764 Running command pip subprocess to install build dependencies 2025-12-16T15:03:49,932 Using pip 23.0.1 from /usr/lib/python3/dist-packages/pip (python 3.11) 2025-12-16T15:03:50,563 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-12-16T15:03:50,586 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-12-16T15:03:52,305 Collecting setuptools>=64 2025-12-16T15:03:52,394 Using cached https://www.piwheels.org/simple/setuptools/setuptools-80.9.0-py3-none-any.whl (1.2 MB) 2025-12-16T15:03:52,777 Collecting setuptools-scm>=8 2025-12-16T15:03:52,796 Using cached https://www.piwheels.org/simple/setuptools-scm/setuptools_scm-9.2.2-py3-none-any.whl (62 kB) 2025-12-16T15:03:52,984 Collecting packaging>=20 2025-12-16T15:03:53,001 Using cached https://www.piwheels.org/simple/packaging/packaging-25.0-py3-none-any.whl (66 kB) 2025-12-16T15:03:55,916 Installing collected packages: setuptools, packaging, setuptools-scm 2025-12-16T15:04:00,031 Creating /tmp/pip-build-env-p_o30ioa/overlay/local/bin 2025-12-16T15:04:00,033 changing mode of /tmp/pip-build-env-p_o30ioa/overlay/local/bin/setuptools-scm to 755 2025-12-16T15:04:00,056 Successfully installed packaging-25.0 setuptools-80.9.0 setuptools-scm-9.2.2 2025-12-16T15:04:00,337 Installing build dependencies: finished with status 'done' 2025-12-16T15:04:00,344 Getting requirements to build wheel: started 2025-12-16T15:04:00,345 Running command Getting requirements to build wheel 2025-12-16T15:04:01,017 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated 2025-12-16T15:04:01,018 !! 2025-12-16T15:04:01,019 ******************************************************************************** 2025-12-16T15:04:01,020 Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0). 2025-12-16T15:04:01,021 By 2026-Feb-18, you need to update your project and remove deprecated calls 2025-12-16T15:04:01,022 or your builds will no longer be supported. 2025-12-16T15:04:01,023 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-12-16T15:04:01,023 ******************************************************************************** 2025-12-16T15:04:01,024 !! 2025-12-16T15:04:01,025 corresp(dist, value, root_dir) 2025-12-16T15:04:01,118 running egg_info 2025-12-16T15:04:01,126 writing seal5.egg-info/PKG-INFO 2025-12-16T15:04:01,130 writing dependency_links to seal5.egg-info/dependency_links.txt 2025-12-16T15:04:01,132 writing entry points to seal5.egg-info/entry_points.txt 2025-12-16T15:04:01,133 writing requirements to seal5.egg-info/requires.txt 2025-12-16T15:04:01,135 writing top-level names to seal5.egg-info/top_level.txt 2025-12-16T15:04:01,184 listing git files failed - pretending there aren't any 2025-12-16T15:04:01,188 reading manifest file 'seal5.egg-info/SOURCES.txt' 2025-12-16T15:04:01,288 adding license file 'LICENSE' 2025-12-16T15:04:01,306 writing manifest file 'seal5.egg-info/SOURCES.txt' 2025-12-16T15:04:01,409 Getting requirements to build wheel: finished with status 'done' 2025-12-16T15:04:01,412 Created temporary directory: /tmp/pip-modern-metadata-e3eok_i7 2025-12-16T15:04:01,414 Preparing metadata (pyproject.toml): started 2025-12-16T15:04:01,416 Running command Preparing metadata (pyproject.toml) 2025-12-16T15:04:02,034 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated 2025-12-16T15:04:02,035 !! 2025-12-16T15:04:02,036 ******************************************************************************** 2025-12-16T15:04:02,036 Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0). 2025-12-16T15:04:02,037 By 2026-Feb-18, you need to update your project and remove deprecated calls 2025-12-16T15:04:02,038 or your builds will no longer be supported. 2025-12-16T15:04:02,039 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-12-16T15:04:02,039 ******************************************************************************** 2025-12-16T15:04:02,041 !! 2025-12-16T15:04:02,041 corresp(dist, value, root_dir) 2025-12-16T15:04:02,129 running dist_info 2025-12-16T15:04:02,143 creating /tmp/pip-modern-metadata-e3eok_i7/seal5.egg-info 2025-12-16T15:04:02,144 writing /tmp/pip-modern-metadata-e3eok_i7/seal5.egg-info/PKG-INFO 2025-12-16T15:04:02,148 writing dependency_links to /tmp/pip-modern-metadata-e3eok_i7/seal5.egg-info/dependency_links.txt 2025-12-16T15:04:02,150 writing entry points to /tmp/pip-modern-metadata-e3eok_i7/seal5.egg-info/entry_points.txt 2025-12-16T15:04:02,151 writing requirements to /tmp/pip-modern-metadata-e3eok_i7/seal5.egg-info/requires.txt 2025-12-16T15:04:02,152 writing top-level names to /tmp/pip-modern-metadata-e3eok_i7/seal5.egg-info/top_level.txt 2025-12-16T15:04:02,154 writing manifest file '/tmp/pip-modern-metadata-e3eok_i7/seal5.egg-info/SOURCES.txt' 2025-12-16T15:04:02,200 listing git files failed - pretending there aren't any 2025-12-16T15:04:02,204 reading manifest file '/tmp/pip-modern-metadata-e3eok_i7/seal5.egg-info/SOURCES.txt' 2025-12-16T15:04:02,207 adding license file 'LICENSE' 2025-12-16T15:04:02,210 writing manifest file '/tmp/pip-modern-metadata-e3eok_i7/seal5.egg-info/SOURCES.txt' 2025-12-16T15:04:02,211 creating '/tmp/pip-modern-metadata-e3eok_i7/seal5-0.3.3.dist-info' 2025-12-16T15:04:02,342 Preparing metadata (pyproject.toml): finished with status 'done' 2025-12-16T15:04:02,348 Source in /tmp/pip-wheel-heqq4gmj/seal5_0c3bdc2122e2459a84a30eea7a40d3a0 has version 0.3.3, which satisfies requirement seal5==0.3.3 from https://files.pythonhosted.org/packages/f6/46/ff32bb0db3b7907b3f9735255eedb74c5b9d66db709a69ce05c055a16cde/seal5-0.3.3.tar.gz 2025-12-16T15:04:02,349 Removed seal5==0.3.3 from https://files.pythonhosted.org/packages/f6/46/ff32bb0db3b7907b3f9735255eedb74c5b9d66db709a69ce05c055a16cde/seal5-0.3.3.tar.gz from build tracker '/tmp/pip-build-tracker-yu7v86hm' 2025-12-16T15:04:02,355 Created temporary directory: /tmp/pip-unpack-okjr43e8 2025-12-16T15:04:02,355 Building wheels for collected packages: seal5 2025-12-16T15:04:02,360 Created temporary directory: /tmp/pip-wheel-wgbks3kz 2025-12-16T15:04:02,360 Destination directory: /tmp/pip-wheel-wgbks3kz 2025-12-16T15:04:02,362 Building wheel for seal5 (pyproject.toml): started 2025-12-16T15:04:02,363 Running command Building wheel for seal5 (pyproject.toml) 2025-12-16T15:04:02,975 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated 2025-12-16T15:04:02,975 !! 2025-12-16T15:04:02,976 ******************************************************************************** 2025-12-16T15:04:02,977 Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0). 2025-12-16T15:04:02,978 By 2026-Feb-18, you need to update your project and remove deprecated calls 2025-12-16T15:04:02,978 or your builds will no longer be supported. 2025-12-16T15:04:02,979 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-12-16T15:04:02,980 ******************************************************************************** 2025-12-16T15:04:02,981 !! 2025-12-16T15:04:02,981 corresp(dist, value, root_dir) 2025-12-16T15:04:03,057 running bdist_wheel 2025-12-16T15:04:03,083 running build 2025-12-16T15:04:03,084 running build_py 2025-12-16T15:04:03,092 creating build/lib/seal5 2025-12-16T15:04:03,094 copying seal5/flow.py -> build/lib/seal5 2025-12-16T15:04:03,098 copying seal5/model.py -> build/lib/seal5 2025-12-16T15:04:03,101 copying seal5/dependencies.py -> build/lib/seal5 2025-12-16T15:04:03,103 copying seal5/types.py -> build/lib/seal5 2025-12-16T15:04:03,105 copying seal5/utils.py -> build/lib/seal5 2025-12-16T15:04:03,107 copying seal5/build_cache.py -> build/lib/seal5 2025-12-16T15:04:03,110 copying seal5/passes.py -> build/lib/seal5 2025-12-16T15:04:03,112 copying seal5/metrics.py -> build/lib/seal5 2025-12-16T15:04:03,114 copying seal5/settings.py -> build/lib/seal5 2025-12-16T15:04:03,117 copying seal5/version.py -> build/lib/seal5 2025-12-16T15:04:03,119 copying seal5/index.py -> build/lib/seal5 2025-12-16T15:04:03,121 copying seal5/wrapper.py -> build/lib/seal5 2025-12-16T15:04:03,124 copying seal5/__init__.py -> build/lib/seal5 2025-12-16T15:04:03,125 copying seal5/riscv_utils.py -> build/lib/seal5 2025-12-16T15:04:03,128 copying seal5/logging.py -> build/lib/seal5 2025-12-16T15:04:03,130 copying seal5/pass_list.py -> build/lib/seal5 2025-12-16T15:04:03,134 copying seal5/testgen_utils.py -> build/lib/seal5 2025-12-16T15:04:03,135 copying seal5/model_utils.py -> build/lib/seal5 2025-12-16T15:04:03,137 running egg_info 2025-12-16T15:04:03,151 writing seal5.egg-info/PKG-INFO 2025-12-16T15:04:03,155 writing dependency_links to seal5.egg-info/dependency_links.txt 2025-12-16T15:04:03,156 writing entry points to seal5.egg-info/entry_points.txt 2025-12-16T15:04:03,158 writing requirements to seal5.egg-info/requires.txt 2025-12-16T15:04:03,159 writing top-level names to seal5.egg-info/top_level.txt 2025-12-16T15:04:03,193 listing git files failed - pretending there aren't any 2025-12-16T15:04:03,197 reading manifest file 'seal5.egg-info/SOURCES.txt' 2025-12-16T15:04:03,226 adding license file 'LICENSE' 2025-12-16T15:04:03,244 writing manifest file 'seal5.egg-info/SOURCES.txt' 2025-12-16T15:04:03,257 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends' is absent from the `packages` configuration. 2025-12-16T15:04:03,258 !! 2025-12-16T15:04:03,259 ******************************************************************************** 2025-12-16T15:04:03,259 ############################ 2025-12-16T15:04:03,260 # Package would be ignored # 2025-12-16T15:04:03,260 ############################ 2025-12-16T15:04:03,261 Python recognizes 'seal5.backends' as an importable package[^1], 2025-12-16T15:04:03,261 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,262 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,263 package, please make sure that 'seal5.backends' is explicitly added 2025-12-16T15:04:03,263 to the `packages` configuration field. 2025-12-16T15:04:03,264 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,265 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,265 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,266 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,267 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,268 If you don't want 'seal5.backends' to be distributed and are 2025-12-16T15:04:03,268 already explicitly excluding 'seal5.backends' via 2025-12-16T15:04:03,269 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,269 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,270 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,271 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,272 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,273 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,274 even if it does not contain any `.py` files. 2025-12-16T15:04:03,274 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,275 directory, all directories are treated like packages. 2025-12-16T15:04:03,275 ******************************************************************************** 2025-12-16T15:04:03,276 !! 2025-12-16T15:04:03,277 check.warn(importable) 2025-12-16T15:04:03,277 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.coredsl2' is absent from the `packages` configuration. 2025-12-16T15:04:03,278 !! 2025-12-16T15:04:03,279 ******************************************************************************** 2025-12-16T15:04:03,279 ############################ 2025-12-16T15:04:03,280 # Package would be ignored # 2025-12-16T15:04:03,280 ############################ 2025-12-16T15:04:03,281 Python recognizes 'seal5.backends.coredsl2' as an importable package[^1], 2025-12-16T15:04:03,281 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,282 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,283 package, please make sure that 'seal5.backends.coredsl2' is explicitly added 2025-12-16T15:04:03,283 to the `packages` configuration field. 2025-12-16T15:04:03,285 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,285 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,285 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,286 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,287 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,287 If you don't want 'seal5.backends.coredsl2' to be distributed and are 2025-12-16T15:04:03,288 already explicitly excluding 'seal5.backends.coredsl2' via 2025-12-16T15:04:03,288 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,288 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,289 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,290 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,290 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,291 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,292 even if it does not contain any `.py` files. 2025-12-16T15:04:03,292 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,293 directory, all directories are treated like packages. 2025-12-16T15:04:03,293 ******************************************************************************** 2025-12-16T15:04:03,294 !! 2025-12-16T15:04:03,294 check.warn(importable) 2025-12-16T15:04:03,295 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.llvmir' is absent from the `packages` configuration. 2025-12-16T15:04:03,295 !! 2025-12-16T15:04:03,296 ******************************************************************************** 2025-12-16T15:04:03,297 ############################ 2025-12-16T15:04:03,297 # Package would be ignored # 2025-12-16T15:04:03,298 ############################ 2025-12-16T15:04:03,298 Python recognizes 'seal5.backends.llvmir' as an importable package[^1], 2025-12-16T15:04:03,298 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,299 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,300 package, please make sure that 'seal5.backends.llvmir' is explicitly added 2025-12-16T15:04:03,300 to the `packages` configuration field. 2025-12-16T15:04:03,301 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,302 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,302 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,303 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,304 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,305 If you don't want 'seal5.backends.llvmir' to be distributed and are 2025-12-16T15:04:03,305 already explicitly excluding 'seal5.backends.llvmir' via 2025-12-16T15:04:03,306 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,306 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,307 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,308 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,309 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,310 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,310 even if it does not contain any `.py` files. 2025-12-16T15:04:03,311 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,311 directory, all directories are treated like packages. 2025-12-16T15:04:03,311 ******************************************************************************** 2025-12-16T15:04:03,312 !! 2025-12-16T15:04:03,312 check.warn(importable) 2025-12-16T15:04:03,313 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.patterngen' is absent from the `packages` configuration. 2025-12-16T15:04:03,313 !! 2025-12-16T15:04:03,314 ******************************************************************************** 2025-12-16T15:04:03,314 ############################ 2025-12-16T15:04:03,315 # Package would be ignored # 2025-12-16T15:04:03,315 ############################ 2025-12-16T15:04:03,316 Python recognizes 'seal5.backends.patterngen' as an importable package[^1], 2025-12-16T15:04:03,316 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,317 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,317 package, please make sure that 'seal5.backends.patterngen' is explicitly added 2025-12-16T15:04:03,318 to the `packages` configuration field. 2025-12-16T15:04:03,318 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,319 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,319 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,320 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,321 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,322 If you don't want 'seal5.backends.patterngen' to be distributed and are 2025-12-16T15:04:03,323 already explicitly excluding 'seal5.backends.patterngen' via 2025-12-16T15:04:03,323 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,324 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,324 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,325 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,326 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,327 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,328 even if it does not contain any `.py` files. 2025-12-16T15:04:03,328 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,329 directory, all directories are treated like packages. 2025-12-16T15:04:03,329 ******************************************************************************** 2025-12-16T15:04:03,330 !! 2025-12-16T15:04:03,330 check.warn(importable) 2025-12-16T15:04:03,331 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report' is absent from the `packages` configuration. 2025-12-16T15:04:03,331 !! 2025-12-16T15:04:03,332 ******************************************************************************** 2025-12-16T15:04:03,333 ############################ 2025-12-16T15:04:03,333 # Package would be ignored # 2025-12-16T15:04:03,334 ############################ 2025-12-16T15:04:03,335 Python recognizes 'seal5.backends.report' as an importable package[^1], 2025-12-16T15:04:03,335 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,336 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,336 package, please make sure that 'seal5.backends.report' is explicitly added 2025-12-16T15:04:03,336 to the `packages` configuration field. 2025-12-16T15:04:03,337 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,337 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,338 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,338 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,339 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,340 If you don't want 'seal5.backends.report' to be distributed and are 2025-12-16T15:04:03,340 already explicitly excluding 'seal5.backends.report' via 2025-12-16T15:04:03,341 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,341 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,342 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,343 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,343 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,345 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,345 even if it does not contain any `.py` files. 2025-12-16T15:04:03,346 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,346 directory, all directories are treated like packages. 2025-12-16T15:04:03,347 ******************************************************************************** 2025-12-16T15:04:03,348 !! 2025-12-16T15:04:03,348 check.warn(importable) 2025-12-16T15:04:03,349 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.diff' is absent from the `packages` configuration. 2025-12-16T15:04:03,349 !! 2025-12-16T15:04:03,350 ******************************************************************************** 2025-12-16T15:04:03,351 ############################ 2025-12-16T15:04:03,351 # Package would be ignored # 2025-12-16T15:04:03,352 ############################ 2025-12-16T15:04:03,352 Python recognizes 'seal5.backends.report.diff' as an importable package[^1], 2025-12-16T15:04:03,352 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,353 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,354 package, please make sure that 'seal5.backends.report.diff' is explicitly added 2025-12-16T15:04:03,354 to the `packages` configuration field. 2025-12-16T15:04:03,355 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,356 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,356 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,357 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,358 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,359 If you don't want 'seal5.backends.report.diff' to be distributed and are 2025-12-16T15:04:03,360 already explicitly excluding 'seal5.backends.report.diff' via 2025-12-16T15:04:03,360 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,361 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,362 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,362 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,363 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,364 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,365 even if it does not contain any `.py` files. 2025-12-16T15:04:03,365 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,365 directory, all directories are treated like packages. 2025-12-16T15:04:03,366 ******************************************************************************** 2025-12-16T15:04:03,366 !! 2025-12-16T15:04:03,367 check.warn(importable) 2025-12-16T15:04:03,367 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.pattern_gen' is absent from the `packages` configuration. 2025-12-16T15:04:03,368 !! 2025-12-16T15:04:03,369 ******************************************************************************** 2025-12-16T15:04:03,369 ############################ 2025-12-16T15:04:03,369 # Package would be ignored # 2025-12-16T15:04:03,370 ############################ 2025-12-16T15:04:03,370 Python recognizes 'seal5.backends.report.pattern_gen' as an importable package[^1], 2025-12-16T15:04:03,371 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,372 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,372 package, please make sure that 'seal5.backends.report.pattern_gen' is explicitly added 2025-12-16T15:04:03,372 to the `packages` configuration field. 2025-12-16T15:04:03,373 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,374 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,374 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,375 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,376 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,377 If you don't want 'seal5.backends.report.pattern_gen' to be distributed and are 2025-12-16T15:04:03,377 already explicitly excluding 'seal5.backends.report.pattern_gen' via 2025-12-16T15:04:03,378 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,378 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,379 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,380 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,381 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,382 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,383 even if it does not contain any `.py` files. 2025-12-16T15:04:03,383 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,384 directory, all directories are treated like packages. 2025-12-16T15:04:03,384 ******************************************************************************** 2025-12-16T15:04:03,385 !! 2025-12-16T15:04:03,386 check.warn(importable) 2025-12-16T15:04:03,386 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.properties' is absent from the `packages` configuration. 2025-12-16T15:04:03,387 !! 2025-12-16T15:04:03,388 ******************************************************************************** 2025-12-16T15:04:03,388 ############################ 2025-12-16T15:04:03,389 # Package would be ignored # 2025-12-16T15:04:03,389 ############################ 2025-12-16T15:04:03,389 Python recognizes 'seal5.backends.report.properties' as an importable package[^1], 2025-12-16T15:04:03,390 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,390 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,391 package, please make sure that 'seal5.backends.report.properties' is explicitly added 2025-12-16T15:04:03,391 to the `packages` configuration field. 2025-12-16T15:04:03,392 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,392 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,393 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,394 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,394 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,395 If you don't want 'seal5.backends.report.properties' to be distributed and are 2025-12-16T15:04:03,396 already explicitly excluding 'seal5.backends.report.properties' via 2025-12-16T15:04:03,396 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,396 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,397 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,398 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,399 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,400 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,401 even if it does not contain any `.py` files. 2025-12-16T15:04:03,401 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,402 directory, all directories are treated like packages. 2025-12-16T15:04:03,402 ******************************************************************************** 2025-12-16T15:04:03,404 !! 2025-12-16T15:04:03,404 check.warn(importable) 2025-12-16T15:04:03,404 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.status' is absent from the `packages` configuration. 2025-12-16T15:04:03,405 !! 2025-12-16T15:04:03,406 ******************************************************************************** 2025-12-16T15:04:03,406 ############################ 2025-12-16T15:04:03,407 # Package would be ignored # 2025-12-16T15:04:03,407 ############################ 2025-12-16T15:04:03,408 Python recognizes 'seal5.backends.report.status' as an importable package[^1], 2025-12-16T15:04:03,408 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,409 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,410 package, please make sure that 'seal5.backends.report.status' is explicitly added 2025-12-16T15:04:03,410 to the `packages` configuration field. 2025-12-16T15:04:03,411 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,412 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,412 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,413 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,414 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,414 If you don't want 'seal5.backends.report.status' to be distributed and are 2025-12-16T15:04:03,415 already explicitly excluding 'seal5.backends.report.status' via 2025-12-16T15:04:03,415 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,415 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,416 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,417 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,417 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,419 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,419 even if it does not contain any `.py` files. 2025-12-16T15:04:03,420 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,420 directory, all directories are treated like packages. 2025-12-16T15:04:03,421 ******************************************************************************** 2025-12-16T15:04:03,421 !! 2025-12-16T15:04:03,422 check.warn(importable) 2025-12-16T15:04:03,422 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.test_results' is absent from the `packages` configuration. 2025-12-16T15:04:03,423 !! 2025-12-16T15:04:03,424 ******************************************************************************** 2025-12-16T15:04:03,424 ############################ 2025-12-16T15:04:03,425 # Package would be ignored # 2025-12-16T15:04:03,425 ############################ 2025-12-16T15:04:03,426 Python recognizes 'seal5.backends.report.test_results' as an importable package[^1], 2025-12-16T15:04:03,426 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,427 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,428 package, please make sure that 'seal5.backends.report.test_results' is explicitly added 2025-12-16T15:04:03,428 to the `packages` configuration field. 2025-12-16T15:04:03,429 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,429 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,430 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,431 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,432 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,433 If you don't want 'seal5.backends.report.test_results' to be distributed and are 2025-12-16T15:04:03,433 already explicitly excluding 'seal5.backends.report.test_results' via 2025-12-16T15:04:03,434 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,434 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,435 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,436 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,437 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,439 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,439 even if it does not contain any `.py` files. 2025-12-16T15:04:03,439 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,440 directory, all directories are treated like packages. 2025-12-16T15:04:03,440 ******************************************************************************** 2025-12-16T15:04:03,441 !! 2025-12-16T15:04:03,441 check.warn(importable) 2025-12-16T15:04:03,441 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.times' is absent from the `packages` configuration. 2025-12-16T15:04:03,442 !! 2025-12-16T15:04:03,442 ******************************************************************************** 2025-12-16T15:04:03,443 ############################ 2025-12-16T15:04:03,443 # Package would be ignored # 2025-12-16T15:04:03,444 ############################ 2025-12-16T15:04:03,444 Python recognizes 'seal5.backends.report.times' as an importable package[^1], 2025-12-16T15:04:03,444 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,445 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,446 package, please make sure that 'seal5.backends.report.times' is explicitly added 2025-12-16T15:04:03,446 to the `packages` configuration field. 2025-12-16T15:04:03,447 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,447 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,448 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,448 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,449 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,450 If you don't want 'seal5.backends.report.times' to be distributed and are 2025-12-16T15:04:03,451 already explicitly excluding 'seal5.backends.report.times' via 2025-12-16T15:04:03,451 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,452 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,453 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,454 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,455 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,456 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,457 even if it does not contain any `.py` files. 2025-12-16T15:04:03,457 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,457 directory, all directories are treated like packages. 2025-12-16T15:04:03,458 ******************************************************************************** 2025-12-16T15:04:03,459 !! 2025-12-16T15:04:03,459 check.warn(importable) 2025-12-16T15:04:03,460 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_features' is absent from the `packages` configuration. 2025-12-16T15:04:03,460 !! 2025-12-16T15:04:03,461 ******************************************************************************** 2025-12-16T15:04:03,462 ############################ 2025-12-16T15:04:03,462 # Package would be ignored # 2025-12-16T15:04:03,463 ############################ 2025-12-16T15:04:03,463 Python recognizes 'seal5.backends.riscv_features' as an importable package[^1], 2025-12-16T15:04:03,464 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,465 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,465 package, please make sure that 'seal5.backends.riscv_features' is explicitly added 2025-12-16T15:04:03,465 to the `packages` configuration field. 2025-12-16T15:04:03,466 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,467 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,467 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,468 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,468 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,469 If you don't want 'seal5.backends.riscv_features' to be distributed and are 2025-12-16T15:04:03,469 already explicitly excluding 'seal5.backends.riscv_features' via 2025-12-16T15:04:03,470 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,470 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,471 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,471 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,472 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,473 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,474 even if it does not contain any `.py` files. 2025-12-16T15:04:03,474 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,475 directory, all directories are treated like packages. 2025-12-16T15:04:03,475 ******************************************************************************** 2025-12-16T15:04:03,476 !! 2025-12-16T15:04:03,476 check.warn(importable) 2025-12-16T15:04:03,477 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_features.templates' is absent from the `packages` configuration. 2025-12-16T15:04:03,477 !! 2025-12-16T15:04:03,479 ******************************************************************************** 2025-12-16T15:04:03,479 ############################ 2025-12-16T15:04:03,480 # Package would be ignored # 2025-12-16T15:04:03,480 ############################ 2025-12-16T15:04:03,481 Python recognizes 'seal5.backends.riscv_features.templates' as an importable package[^1], 2025-12-16T15:04:03,481 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,482 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,482 package, please make sure that 'seal5.backends.riscv_features.templates' is explicitly added 2025-12-16T15:04:03,483 to the `packages` configuration field. 2025-12-16T15:04:03,484 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,484 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,485 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,486 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,487 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,488 If you don't want 'seal5.backends.riscv_features.templates' to be distributed and are 2025-12-16T15:04:03,489 already explicitly excluding 'seal5.backends.riscv_features.templates' via 2025-12-16T15:04:03,489 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,490 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,490 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,491 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,492 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,493 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,493 even if it does not contain any `.py` files. 2025-12-16T15:04:03,494 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,494 directory, all directories are treated like packages. 2025-12-16T15:04:03,494 ******************************************************************************** 2025-12-16T15:04:03,495 !! 2025-12-16T15:04:03,495 check.warn(importable) 2025-12-16T15:04:03,496 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_field_types' is absent from the `packages` configuration. 2025-12-16T15:04:03,496 !! 2025-12-16T15:04:03,497 ******************************************************************************** 2025-12-16T15:04:03,497 ############################ 2025-12-16T15:04:03,498 # Package would be ignored # 2025-12-16T15:04:03,498 ############################ 2025-12-16T15:04:03,498 Python recognizes 'seal5.backends.riscv_field_types' as an importable package[^1], 2025-12-16T15:04:03,499 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,500 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,500 package, please make sure that 'seal5.backends.riscv_field_types' is explicitly added 2025-12-16T15:04:03,501 to the `packages` configuration field. 2025-12-16T15:04:03,502 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,502 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,503 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,504 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,505 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,506 If you don't want 'seal5.backends.riscv_field_types' to be distributed and are 2025-12-16T15:04:03,506 already explicitly excluding 'seal5.backends.riscv_field_types' via 2025-12-16T15:04:03,507 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,507 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,508 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,508 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,509 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,511 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,511 even if it does not contain any `.py` files. 2025-12-16T15:04:03,512 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,512 directory, all directories are treated like packages. 2025-12-16T15:04:03,513 ******************************************************************************** 2025-12-16T15:04:03,514 !! 2025-12-16T15:04:03,514 check.warn(importable) 2025-12-16T15:04:03,515 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_gisel_legalizer' is absent from the `packages` configuration. 2025-12-16T15:04:03,516 !! 2025-12-16T15:04:03,517 ******************************************************************************** 2025-12-16T15:04:03,517 ############################ 2025-12-16T15:04:03,517 # Package would be ignored # 2025-12-16T15:04:03,518 ############################ 2025-12-16T15:04:03,518 Python recognizes 'seal5.backends.riscv_gisel_legalizer' as an importable package[^1], 2025-12-16T15:04:03,518 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,519 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,519 package, please make sure that 'seal5.backends.riscv_gisel_legalizer' is explicitly added 2025-12-16T15:04:03,520 to the `packages` configuration field. 2025-12-16T15:04:03,520 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,521 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,521 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,522 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,523 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,524 If you don't want 'seal5.backends.riscv_gisel_legalizer' to be distributed and are 2025-12-16T15:04:03,524 already explicitly excluding 'seal5.backends.riscv_gisel_legalizer' via 2025-12-16T15:04:03,525 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,525 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,525 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,526 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,527 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,528 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,529 even if it does not contain any `.py` files. 2025-12-16T15:04:03,529 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,530 directory, all directories are treated like packages. 2025-12-16T15:04:03,531 ******************************************************************************** 2025-12-16T15:04:03,532 !! 2025-12-16T15:04:03,532 check.warn(importable) 2025-12-16T15:04:03,533 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_instr_info' is absent from the `packages` configuration. 2025-12-16T15:04:03,533 !! 2025-12-16T15:04:03,534 ******************************************************************************** 2025-12-16T15:04:03,534 ############################ 2025-12-16T15:04:03,535 # Package would be ignored # 2025-12-16T15:04:03,535 ############################ 2025-12-16T15:04:03,536 Python recognizes 'seal5.backends.riscv_instr_info' as an importable package[^1], 2025-12-16T15:04:03,536 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,537 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,538 package, please make sure that 'seal5.backends.riscv_instr_info' is explicitly added 2025-12-16T15:04:03,538 to the `packages` configuration field. 2025-12-16T15:04:03,540 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,540 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,541 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,542 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,542 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,543 If you don't want 'seal5.backends.riscv_instr_info' to be distributed and are 2025-12-16T15:04:03,543 already explicitly excluding 'seal5.backends.riscv_instr_info' via 2025-12-16T15:04:03,544 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,544 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,544 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,545 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,546 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,547 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,548 even if it does not contain any `.py` files. 2025-12-16T15:04:03,548 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,549 directory, all directories are treated like packages. 2025-12-16T15:04:03,549 ******************************************************************************** 2025-12-16T15:04:03,550 !! 2025-12-16T15:04:03,550 check.warn(importable) 2025-12-16T15:04:03,550 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_instr_info.templates' is absent from the `packages` configuration. 2025-12-16T15:04:03,551 !! 2025-12-16T15:04:03,552 ******************************************************************************** 2025-12-16T15:04:03,552 ############################ 2025-12-16T15:04:03,553 # Package would be ignored # 2025-12-16T15:04:03,553 ############################ 2025-12-16T15:04:03,553 Python recognizes 'seal5.backends.riscv_instr_info.templates' as an importable package[^1], 2025-12-16T15:04:03,554 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,554 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,555 package, please make sure that 'seal5.backends.riscv_instr_info.templates' is explicitly added 2025-12-16T15:04:03,555 to the `packages` configuration field. 2025-12-16T15:04:03,557 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,557 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,558 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,558 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,559 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,560 If you don't want 'seal5.backends.riscv_instr_info.templates' to be distributed and are 2025-12-16T15:04:03,561 already explicitly excluding 'seal5.backends.riscv_instr_info.templates' via 2025-12-16T15:04:03,561 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,562 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,562 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,563 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,564 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,565 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,566 even if it does not contain any `.py` files. 2025-12-16T15:04:03,566 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,566 directory, all directories are treated like packages. 2025-12-16T15:04:03,567 ******************************************************************************** 2025-12-16T15:04:03,567 !! 2025-12-16T15:04:03,568 check.warn(importable) 2025-12-16T15:04:03,568 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_intrinsics' is absent from the `packages` configuration. 2025-12-16T15:04:03,568 !! 2025-12-16T15:04:03,569 ******************************************************************************** 2025-12-16T15:04:03,569 ############################ 2025-12-16T15:04:03,570 # Package would be ignored # 2025-12-16T15:04:03,570 ############################ 2025-12-16T15:04:03,571 Python recognizes 'seal5.backends.riscv_intrinsics' as an importable package[^1], 2025-12-16T15:04:03,571 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,572 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,572 package, please make sure that 'seal5.backends.riscv_intrinsics' is explicitly added 2025-12-16T15:04:03,573 to the `packages` configuration field. 2025-12-16T15:04:03,573 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,574 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,574 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,575 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,576 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,577 If you don't want 'seal5.backends.riscv_intrinsics' to be distributed and are 2025-12-16T15:04:03,577 already explicitly excluding 'seal5.backends.riscv_intrinsics' via 2025-12-16T15:04:03,578 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,578 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,579 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,580 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,580 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,582 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,582 even if it does not contain any `.py` files. 2025-12-16T15:04:03,583 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,583 directory, all directories are treated like packages. 2025-12-16T15:04:03,583 ******************************************************************************** 2025-12-16T15:04:03,584 !! 2025-12-16T15:04:03,585 check.warn(importable) 2025-12-16T15:04:03,585 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_isa_info' is absent from the `packages` configuration. 2025-12-16T15:04:03,586 !! 2025-12-16T15:04:03,587 ******************************************************************************** 2025-12-16T15:04:03,587 ############################ 2025-12-16T15:04:03,588 # Package would be ignored # 2025-12-16T15:04:03,588 ############################ 2025-12-16T15:04:03,589 Python recognizes 'seal5.backends.riscv_isa_info' as an importable package[^1], 2025-12-16T15:04:03,589 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,590 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,590 package, please make sure that 'seal5.backends.riscv_isa_info' is explicitly added 2025-12-16T15:04:03,591 to the `packages` configuration field. 2025-12-16T15:04:03,592 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,592 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,592 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,593 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,594 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,594 If you don't want 'seal5.backends.riscv_isa_info' to be distributed and are 2025-12-16T15:04:03,595 already explicitly excluding 'seal5.backends.riscv_isa_info' via 2025-12-16T15:04:03,595 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,596 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,596 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,597 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,598 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,599 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,599 even if it does not contain any `.py` files. 2025-12-16T15:04:03,600 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,600 directory, all directories are treated like packages. 2025-12-16T15:04:03,601 ******************************************************************************** 2025-12-16T15:04:03,601 !! 2025-12-16T15:04:03,602 check.warn(importable) 2025-12-16T15:04:03,602 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_register_info' is absent from the `packages` configuration. 2025-12-16T15:04:03,603 !! 2025-12-16T15:04:03,604 ******************************************************************************** 2025-12-16T15:04:03,604 ############################ 2025-12-16T15:04:03,605 # Package would be ignored # 2025-12-16T15:04:03,605 ############################ 2025-12-16T15:04:03,605 Python recognizes 'seal5.backends.riscv_register_info' as an importable package[^1], 2025-12-16T15:04:03,606 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,607 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,607 package, please make sure that 'seal5.backends.riscv_register_info' is explicitly added 2025-12-16T15:04:03,607 to the `packages` configuration field. 2025-12-16T15:04:03,608 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,609 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,609 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,610 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,611 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,612 If you don't want 'seal5.backends.riscv_register_info' to be distributed and are 2025-12-16T15:04:03,612 already explicitly excluding 'seal5.backends.riscv_register_info' via 2025-12-16T15:04:03,613 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,614 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,614 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,615 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,615 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,616 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,617 even if it does not contain any `.py` files. 2025-12-16T15:04:03,617 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,617 directory, all directories are treated like packages. 2025-12-16T15:04:03,618 ******************************************************************************** 2025-12-16T15:04:03,619 !! 2025-12-16T15:04:03,619 check.warn(importable) 2025-12-16T15:04:03,619 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.viewer_seal5' is absent from the `packages` configuration. 2025-12-16T15:04:03,620 !! 2025-12-16T15:04:03,621 ******************************************************************************** 2025-12-16T15:04:03,621 ############################ 2025-12-16T15:04:03,621 # Package would be ignored # 2025-12-16T15:04:03,622 ############################ 2025-12-16T15:04:03,622 Python recognizes 'seal5.backends.viewer_seal5' as an importable package[^1], 2025-12-16T15:04:03,623 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,624 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,624 package, please make sure that 'seal5.backends.viewer_seal5' is explicitly added 2025-12-16T15:04:03,625 to the `packages` configuration field. 2025-12-16T15:04:03,626 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,626 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,626 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,627 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,628 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,629 If you don't want 'seal5.backends.viewer_seal5' to be distributed and are 2025-12-16T15:04:03,629 already explicitly excluding 'seal5.backends.viewer_seal5' via 2025-12-16T15:04:03,630 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,630 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,631 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,632 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,633 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,634 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,635 even if it does not contain any `.py` files. 2025-12-16T15:04:03,635 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,635 directory, all directories are treated like packages. 2025-12-16T15:04:03,636 ******************************************************************************** 2025-12-16T15:04:03,637 !! 2025-12-16T15:04:03,637 check.warn(importable) 2025-12-16T15:04:03,638 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.yaml' is absent from the `packages` configuration. 2025-12-16T15:04:03,638 !! 2025-12-16T15:04:03,639 ******************************************************************************** 2025-12-16T15:04:03,639 ############################ 2025-12-16T15:04:03,640 # Package would be ignored # 2025-12-16T15:04:03,640 ############################ 2025-12-16T15:04:03,640 Python recognizes 'seal5.backends.yaml' as an importable package[^1], 2025-12-16T15:04:03,641 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,642 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,642 package, please make sure that 'seal5.backends.yaml' is explicitly added 2025-12-16T15:04:03,642 to the `packages` configuration field. 2025-12-16T15:04:03,643 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,643 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,644 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,645 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,645 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,646 If you don't want 'seal5.backends.yaml' to be distributed and are 2025-12-16T15:04:03,646 already explicitly excluding 'seal5.backends.yaml' via 2025-12-16T15:04:03,647 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,647 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,648 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,649 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,649 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,651 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,651 even if it does not contain any `.py` files. 2025-12-16T15:04:03,652 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,652 directory, all directories are treated like packages. 2025-12-16T15:04:03,653 ******************************************************************************** 2025-12-16T15:04:03,653 !! 2025-12-16T15:04:03,654 check.warn(importable) 2025-12-16T15:04:03,654 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.cli' is absent from the `packages` configuration. 2025-12-16T15:04:03,655 !! 2025-12-16T15:04:03,656 ******************************************************************************** 2025-12-16T15:04:03,656 ############################ 2025-12-16T15:04:03,656 # Package would be ignored # 2025-12-16T15:04:03,657 ############################ 2025-12-16T15:04:03,657 Python recognizes 'seal5.cli' as an importable package[^1], 2025-12-16T15:04:03,658 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,659 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,659 package, please make sure that 'seal5.cli' is explicitly added 2025-12-16T15:04:03,660 to the `packages` configuration field. 2025-12-16T15:04:03,661 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,661 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,661 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,663 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,663 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,664 If you don't want 'seal5.cli' to be distributed and are 2025-12-16T15:04:03,664 already explicitly excluding 'seal5.cli' via 2025-12-16T15:04:03,665 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,665 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,665 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,666 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,667 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,668 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,668 even if it does not contain any `.py` files. 2025-12-16T15:04:03,669 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,669 directory, all directories are treated like packages. 2025-12-16T15:04:03,670 ******************************************************************************** 2025-12-16T15:04:03,670 !! 2025-12-16T15:04:03,671 check.warn(importable) 2025-12-16T15:04:03,671 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.frontends.coredsl2_seal5' is absent from the `packages` configuration. 2025-12-16T15:04:03,672 !! 2025-12-16T15:04:03,672 ******************************************************************************** 2025-12-16T15:04:03,673 ############################ 2025-12-16T15:04:03,673 # Package would be ignored # 2025-12-16T15:04:03,674 ############################ 2025-12-16T15:04:03,674 Python recognizes 'seal5.frontends.coredsl2_seal5' as an importable package[^1], 2025-12-16T15:04:03,675 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,675 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,676 package, please make sure that 'seal5.frontends.coredsl2_seal5' is explicitly added 2025-12-16T15:04:03,676 to the `packages` configuration field. 2025-12-16T15:04:03,677 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,678 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,678 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,679 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,680 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,681 If you don't want 'seal5.frontends.coredsl2_seal5' to be distributed and are 2025-12-16T15:04:03,681 already explicitly excluding 'seal5.frontends.coredsl2_seal5' via 2025-12-16T15:04:03,682 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,682 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,683 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,684 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,684 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,686 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,686 even if it does not contain any `.py` files. 2025-12-16T15:04:03,687 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,687 directory, all directories are treated like packages. 2025-12-16T15:04:03,688 ******************************************************************************** 2025-12-16T15:04:03,688 !! 2025-12-16T15:04:03,689 check.warn(importable) 2025-12-16T15:04:03,689 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.frontends.coredsl2_seal5.parser_gen' is absent from the `packages` configuration. 2025-12-16T15:04:03,690 !! 2025-12-16T15:04:03,690 ******************************************************************************** 2025-12-16T15:04:03,691 ############################ 2025-12-16T15:04:03,691 # Package would be ignored # 2025-12-16T15:04:03,692 ############################ 2025-12-16T15:04:03,692 Python recognizes 'seal5.frontends.coredsl2_seal5.parser_gen' as an importable package[^1], 2025-12-16T15:04:03,692 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,693 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,694 package, please make sure that 'seal5.frontends.coredsl2_seal5.parser_gen' is explicitly added 2025-12-16T15:04:03,694 to the `packages` configuration field. 2025-12-16T15:04:03,695 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,695 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,696 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,697 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,697 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,698 If you don't want 'seal5.frontends.coredsl2_seal5.parser_gen' to be distributed and are 2025-12-16T15:04:03,699 already explicitly excluding 'seal5.frontends.coredsl2_seal5.parser_gen' via 2025-12-16T15:04:03,699 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,699 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,700 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,701 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,702 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,703 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,704 even if it does not contain any `.py` files. 2025-12-16T15:04:03,704 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,704 directory, all directories are treated like packages. 2025-12-16T15:04:03,705 ******************************************************************************** 2025-12-16T15:04:03,706 !! 2025-12-16T15:04:03,706 check.warn(importable) 2025-12-16T15:04:03,707 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.resources' is absent from the `packages` configuration. 2025-12-16T15:04:03,707 !! 2025-12-16T15:04:03,708 ******************************************************************************** 2025-12-16T15:04:03,708 ############################ 2025-12-16T15:04:03,709 # Package would be ignored # 2025-12-16T15:04:03,710 ############################ 2025-12-16T15:04:03,710 Python recognizes 'seal5.resources' as an importable package[^1], 2025-12-16T15:04:03,711 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,712 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,712 package, please make sure that 'seal5.resources' is explicitly added 2025-12-16T15:04:03,713 to the `packages` configuration field. 2025-12-16T15:04:03,713 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,714 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,714 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,715 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,716 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,716 If you don't want 'seal5.resources' to be distributed and are 2025-12-16T15:04:03,717 already explicitly excluding 'seal5.resources' via 2025-12-16T15:04:03,717 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,717 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,718 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,719 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,719 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,721 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,721 even if it does not contain any `.py` files. 2025-12-16T15:04:03,721 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,722 directory, all directories are treated like packages. 2025-12-16T15:04:03,722 ******************************************************************************** 2025-12-16T15:04:03,723 !! 2025-12-16T15:04:03,724 check.warn(importable) 2025-12-16T15:04:03,724 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.resources.patches.llvm' is absent from the `packages` configuration. 2025-12-16T15:04:03,724 !! 2025-12-16T15:04:03,725 ******************************************************************************** 2025-12-16T15:04:03,726 ############################ 2025-12-16T15:04:03,726 # Package would be ignored # 2025-12-16T15:04:03,727 ############################ 2025-12-16T15:04:03,727 Python recognizes 'seal5.resources.patches.llvm' as an importable package[^1], 2025-12-16T15:04:03,728 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,729 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,729 package, please make sure that 'seal5.resources.patches.llvm' is explicitly added 2025-12-16T15:04:03,730 to the `packages` configuration field. 2025-12-16T15:04:03,731 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,731 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,732 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,733 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,734 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,734 If you don't want 'seal5.resources.patches.llvm' to be distributed and are 2025-12-16T15:04:03,735 already explicitly excluding 'seal5.resources.patches.llvm' via 2025-12-16T15:04:03,736 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,736 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,736 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,738 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,738 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,740 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,740 even if it does not contain any `.py` files. 2025-12-16T15:04:03,740 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,741 directory, all directories are treated like packages. 2025-12-16T15:04:03,741 ******************************************************************************** 2025-12-16T15:04:03,742 !! 2025-12-16T15:04:03,742 check.warn(importable) 2025-12-16T15:04:03,742 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.tools' is absent from the `packages` configuration. 2025-12-16T15:04:03,743 !! 2025-12-16T15:04:03,744 ******************************************************************************** 2025-12-16T15:04:03,744 ############################ 2025-12-16T15:04:03,745 # Package would be ignored # 2025-12-16T15:04:03,745 ############################ 2025-12-16T15:04:03,745 Python recognizes 'seal5.tools' as an importable package[^1], 2025-12-16T15:04:03,746 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,747 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,747 package, please make sure that 'seal5.tools' is explicitly added 2025-12-16T15:04:03,748 to the `packages` configuration field. 2025-12-16T15:04:03,748 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,749 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,749 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,750 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,751 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,752 If you don't want 'seal5.tools' to be distributed and are 2025-12-16T15:04:03,752 already explicitly excluding 'seal5.tools' via 2025-12-16T15:04:03,753 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,753 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,754 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,755 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,755 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,757 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,757 even if it does not contain any `.py` files. 2025-12-16T15:04:03,758 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,758 directory, all directories are treated like packages. 2025-12-16T15:04:03,759 ******************************************************************************** 2025-12-16T15:04:03,760 !! 2025-12-16T15:04:03,760 check.warn(importable) 2025-12-16T15:04:03,761 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform' is absent from the `packages` configuration. 2025-12-16T15:04:03,761 !! 2025-12-16T15:04:03,762 ******************************************************************************** 2025-12-16T15:04:03,763 ############################ 2025-12-16T15:04:03,764 # Package would be ignored # 2025-12-16T15:04:03,764 ############################ 2025-12-16T15:04:03,764 Python recognizes 'seal5.transform' as an importable package[^1], 2025-12-16T15:04:03,765 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,765 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,766 package, please make sure that 'seal5.transform' is explicitly added 2025-12-16T15:04:03,766 to the `packages` configuration field. 2025-12-16T15:04:03,767 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,767 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,768 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,768 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,769 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,770 If you don't want 'seal5.transform' to be distributed and are 2025-12-16T15:04:03,770 already explicitly excluding 'seal5.transform' via 2025-12-16T15:04:03,771 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,771 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,771 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,772 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,773 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,775 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,775 even if it does not contain any `.py` files. 2025-12-16T15:04:03,776 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,776 directory, all directories are treated like packages. 2025-12-16T15:04:03,777 ******************************************************************************** 2025-12-16T15:04:03,778 !! 2025-12-16T15:04:03,778 check.warn(importable) 2025-12-16T15:04:03,779 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.annotate_opcodes' is absent from the `packages` configuration. 2025-12-16T15:04:03,779 !! 2025-12-16T15:04:03,780 ******************************************************************************** 2025-12-16T15:04:03,781 ############################ 2025-12-16T15:04:03,781 # Package would be ignored # 2025-12-16T15:04:03,782 ############################ 2025-12-16T15:04:03,782 Python recognizes 'seal5.transform.annotate_opcodes' as an importable package[^1], 2025-12-16T15:04:03,783 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,784 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,784 package, please make sure that 'seal5.transform.annotate_opcodes' is explicitly added 2025-12-16T15:04:03,784 to the `packages` configuration field. 2025-12-16T15:04:03,785 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,786 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,787 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,788 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,789 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,790 If you don't want 'seal5.transform.annotate_opcodes' to be distributed and are 2025-12-16T15:04:03,790 already explicitly excluding 'seal5.transform.annotate_opcodes' via 2025-12-16T15:04:03,791 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,791 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,792 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,792 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,793 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,794 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,794 even if it does not contain any `.py` files. 2025-12-16T15:04:03,795 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,795 directory, all directories are treated like packages. 2025-12-16T15:04:03,795 ******************************************************************************** 2025-12-16T15:04:03,796 !! 2025-12-16T15:04:03,797 check.warn(importable) 2025-12-16T15:04:03,797 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.check_pattern_support' is absent from the `packages` configuration. 2025-12-16T15:04:03,797 !! 2025-12-16T15:04:03,798 ******************************************************************************** 2025-12-16T15:04:03,798 ############################ 2025-12-16T15:04:03,799 # Package would be ignored # 2025-12-16T15:04:03,799 ############################ 2025-12-16T15:04:03,800 Python recognizes 'seal5.transform.check_pattern_support' as an importable package[^1], 2025-12-16T15:04:03,800 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,801 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,802 package, please make sure that 'seal5.transform.check_pattern_support' is explicitly added 2025-12-16T15:04:03,802 to the `packages` configuration field. 2025-12-16T15:04:03,803 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,804 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,804 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,806 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,807 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,807 If you don't want 'seal5.transform.check_pattern_support' to be distributed and are 2025-12-16T15:04:03,808 already explicitly excluding 'seal5.transform.check_pattern_support' via 2025-12-16T15:04:03,808 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,809 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,809 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,810 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,811 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,813 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,813 even if it does not contain any `.py` files. 2025-12-16T15:04:03,814 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,814 directory, all directories are treated like packages. 2025-12-16T15:04:03,815 ******************************************************************************** 2025-12-16T15:04:03,816 !! 2025-12-16T15:04:03,816 check.warn(importable) 2025-12-16T15:04:03,817 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.collect_immediate_operands' is absent from the `packages` configuration. 2025-12-16T15:04:03,817 !! 2025-12-16T15:04:03,818 ******************************************************************************** 2025-12-16T15:04:03,818 ############################ 2025-12-16T15:04:03,818 # Package would be ignored # 2025-12-16T15:04:03,819 ############################ 2025-12-16T15:04:03,819 Python recognizes 'seal5.transform.collect_immediate_operands' as an importable package[^1], 2025-12-16T15:04:03,820 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,820 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,821 package, please make sure that 'seal5.transform.collect_immediate_operands' is explicitly added 2025-12-16T15:04:03,821 to the `packages` configuration field. 2025-12-16T15:04:03,822 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,822 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,823 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,824 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,824 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,825 If you don't want 'seal5.transform.collect_immediate_operands' to be distributed and are 2025-12-16T15:04:03,826 already explicitly excluding 'seal5.transform.collect_immediate_operands' via 2025-12-16T15:04:03,826 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,826 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,827 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,828 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,829 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,830 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,831 even if it does not contain any `.py` files. 2025-12-16T15:04:03,831 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,832 directory, all directories are treated like packages. 2025-12-16T15:04:03,832 ******************************************************************************** 2025-12-16T15:04:03,833 !! 2025-12-16T15:04:03,834 check.warn(importable) 2025-12-16T15:04:03,834 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.collect_operand_types' is absent from the `packages` configuration. 2025-12-16T15:04:03,835 !! 2025-12-16T15:04:03,836 ******************************************************************************** 2025-12-16T15:04:03,836 ############################ 2025-12-16T15:04:03,837 # Package would be ignored # 2025-12-16T15:04:03,837 ############################ 2025-12-16T15:04:03,838 Python recognizes 'seal5.transform.collect_operand_types' as an importable package[^1], 2025-12-16T15:04:03,838 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,839 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,840 package, please make sure that 'seal5.transform.collect_operand_types' is explicitly added 2025-12-16T15:04:03,841 to the `packages` configuration field. 2025-12-16T15:04:03,841 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,842 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,842 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,843 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,844 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,845 If you don't want 'seal5.transform.collect_operand_types' to be distributed and are 2025-12-16T15:04:03,845 already explicitly excluding 'seal5.transform.collect_operand_types' via 2025-12-16T15:04:03,846 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,846 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,847 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,847 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,848 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,850 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,850 even if it does not contain any `.py` files. 2025-12-16T15:04:03,851 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,851 directory, all directories are treated like packages. 2025-12-16T15:04:03,852 ******************************************************************************** 2025-12-16T15:04:03,853 !! 2025-12-16T15:04:03,853 check.warn(importable) 2025-12-16T15:04:03,853 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.collect_raises' is absent from the `packages` configuration. 2025-12-16T15:04:03,854 !! 2025-12-16T15:04:03,855 ******************************************************************************** 2025-12-16T15:04:03,855 ############################ 2025-12-16T15:04:03,856 # Package would be ignored # 2025-12-16T15:04:03,856 ############################ 2025-12-16T15:04:03,857 Python recognizes 'seal5.transform.collect_raises' as an importable package[^1], 2025-12-16T15:04:03,857 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,858 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,859 package, please make sure that 'seal5.transform.collect_raises' is explicitly added 2025-12-16T15:04:03,859 to the `packages` configuration field. 2025-12-16T15:04:03,860 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,861 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,861 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,862 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,863 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,864 If you don't want 'seal5.transform.collect_raises' to be distributed and are 2025-12-16T15:04:03,865 already explicitly excluding 'seal5.transform.collect_raises' via 2025-12-16T15:04:03,865 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,866 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,866 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,868 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,869 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,870 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,870 even if it does not contain any `.py` files. 2025-12-16T15:04:03,871 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,871 directory, all directories are treated like packages. 2025-12-16T15:04:03,872 ******************************************************************************** 2025-12-16T15:04:03,873 !! 2025-12-16T15:04:03,873 check.warn(importable) 2025-12-16T15:04:03,873 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.collect_register_operands' is absent from the `packages` configuration. 2025-12-16T15:04:03,874 !! 2025-12-16T15:04:03,875 ******************************************************************************** 2025-12-16T15:04:03,875 ############################ 2025-12-16T15:04:03,875 # Package would be ignored # 2025-12-16T15:04:03,876 ############################ 2025-12-16T15:04:03,876 Python recognizes 'seal5.transform.collect_register_operands' as an importable package[^1], 2025-12-16T15:04:03,877 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,878 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,878 package, please make sure that 'seal5.transform.collect_register_operands' is explicitly added 2025-12-16T15:04:03,879 to the `packages` configuration field. 2025-12-16T15:04:03,880 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,880 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,880 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,881 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,882 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,883 If you don't want 'seal5.transform.collect_register_operands' to be distributed and are 2025-12-16T15:04:03,884 already explicitly excluding 'seal5.transform.collect_register_operands' via 2025-12-16T15:04:03,884 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,885 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,885 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,886 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,887 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,889 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,889 even if it does not contain any `.py` files. 2025-12-16T15:04:03,890 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,890 directory, all directories are treated like packages. 2025-12-16T15:04:03,891 ******************************************************************************** 2025-12-16T15:04:03,892 !! 2025-12-16T15:04:03,893 check.warn(importable) 2025-12-16T15:04:03,893 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_calls' is absent from the `packages` configuration. 2025-12-16T15:04:03,894 !! 2025-12-16T15:04:03,895 ******************************************************************************** 2025-12-16T15:04:03,896 ############################ 2025-12-16T15:04:03,896 # Package would be ignored # 2025-12-16T15:04:03,897 ############################ 2025-12-16T15:04:03,897 Python recognizes 'seal5.transform.detect_calls' as an importable package[^1], 2025-12-16T15:04:03,897 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,898 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,899 package, please make sure that 'seal5.transform.detect_calls' is explicitly added 2025-12-16T15:04:03,899 to the `packages` configuration field. 2025-12-16T15:04:03,900 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,900 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,901 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,902 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,902 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,903 If you don't want 'seal5.transform.detect_calls' to be distributed and are 2025-12-16T15:04:03,904 already explicitly excluding 'seal5.transform.detect_calls' via 2025-12-16T15:04:03,904 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,905 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,905 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,906 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,907 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,909 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,910 even if it does not contain any `.py` files. 2025-12-16T15:04:03,910 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,911 directory, all directories are treated like packages. 2025-12-16T15:04:03,911 ******************************************************************************** 2025-12-16T15:04:03,912 !! 2025-12-16T15:04:03,913 check.warn(importable) 2025-12-16T15:04:03,913 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_imm_leafs' is absent from the `packages` configuration. 2025-12-16T15:04:03,914 !! 2025-12-16T15:04:03,915 ******************************************************************************** 2025-12-16T15:04:03,915 ############################ 2025-12-16T15:04:03,916 # Package would be ignored # 2025-12-16T15:04:03,916 ############################ 2025-12-16T15:04:03,917 Python recognizes 'seal5.transform.detect_imm_leafs' as an importable package[^1], 2025-12-16T15:04:03,917 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,918 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,919 package, please make sure that 'seal5.transform.detect_imm_leafs' is explicitly added 2025-12-16T15:04:03,919 to the `packages` configuration field. 2025-12-16T15:04:03,920 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,921 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,921 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,922 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,924 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,925 If you don't want 'seal5.transform.detect_imm_leafs' to be distributed and are 2025-12-16T15:04:03,925 already explicitly excluding 'seal5.transform.detect_imm_leafs' via 2025-12-16T15:04:03,925 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,926 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,926 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,927 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,928 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,929 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,929 even if it does not contain any `.py` files. 2025-12-16T15:04:03,930 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,930 directory, all directories are treated like packages. 2025-12-16T15:04:03,931 ******************************************************************************** 2025-12-16T15:04:03,932 !! 2025-12-16T15:04:03,932 check.warn(importable) 2025-12-16T15:04:03,933 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_inouts' is absent from the `packages` configuration. 2025-12-16T15:04:03,933 !! 2025-12-16T15:04:03,934 ******************************************************************************** 2025-12-16T15:04:03,934 ############################ 2025-12-16T15:04:03,935 # Package would be ignored # 2025-12-16T15:04:03,936 ############################ 2025-12-16T15:04:03,936 Python recognizes 'seal5.transform.detect_inouts' as an importable package[^1], 2025-12-16T15:04:03,936 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,937 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,938 package, please make sure that 'seal5.transform.detect_inouts' is explicitly added 2025-12-16T15:04:03,938 to the `packages` configuration field. 2025-12-16T15:04:03,939 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,940 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,940 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,941 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,942 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,943 If you don't want 'seal5.transform.detect_inouts' to be distributed and are 2025-12-16T15:04:03,944 already explicitly excluding 'seal5.transform.detect_inouts' via 2025-12-16T15:04:03,944 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,945 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,945 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,946 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,947 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,949 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,949 even if it does not contain any `.py` files. 2025-12-16T15:04:03,950 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,951 directory, all directories are treated like packages. 2025-12-16T15:04:03,951 ******************************************************************************** 2025-12-16T15:04:03,952 !! 2025-12-16T15:04:03,953 check.warn(importable) 2025-12-16T15:04:03,953 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_loops' is absent from the `packages` configuration. 2025-12-16T15:04:03,953 !! 2025-12-16T15:04:03,954 ******************************************************************************** 2025-12-16T15:04:03,955 ############################ 2025-12-16T15:04:03,955 # Package would be ignored # 2025-12-16T15:04:03,956 ############################ 2025-12-16T15:04:03,956 Python recognizes 'seal5.transform.detect_loops' as an importable package[^1], 2025-12-16T15:04:03,957 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,958 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,958 package, please make sure that 'seal5.transform.detect_loops' is explicitly added 2025-12-16T15:04:03,958 to the `packages` configuration field. 2025-12-16T15:04:03,959 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,960 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,960 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,961 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,962 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,963 If you don't want 'seal5.transform.detect_loops' to be distributed and are 2025-12-16T15:04:03,964 already explicitly excluding 'seal5.transform.detect_loops' via 2025-12-16T15:04:03,964 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,965 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,965 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,966 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,967 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,969 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,969 even if it does not contain any `.py` files. 2025-12-16T15:04:03,969 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,970 directory, all directories are treated like packages. 2025-12-16T15:04:03,970 ******************************************************************************** 2025-12-16T15:04:03,971 !! 2025-12-16T15:04:03,972 check.warn(importable) 2025-12-16T15:04:03,972 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_registers' is absent from the `packages` configuration. 2025-12-16T15:04:03,973 !! 2025-12-16T15:04:03,974 ******************************************************************************** 2025-12-16T15:04:03,974 ############################ 2025-12-16T15:04:03,975 # Package would be ignored # 2025-12-16T15:04:03,975 ############################ 2025-12-16T15:04:03,976 Python recognizes 'seal5.transform.detect_registers' as an importable package[^1], 2025-12-16T15:04:03,976 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,977 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,978 package, please make sure that 'seal5.transform.detect_registers' is explicitly added 2025-12-16T15:04:03,979 to the `packages` configuration field. 2025-12-16T15:04:03,980 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,980 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:03,980 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:03,981 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:03,982 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:03,983 If you don't want 'seal5.transform.detect_registers' to be distributed and are 2025-12-16T15:04:03,984 already explicitly excluding 'seal5.transform.detect_registers' via 2025-12-16T15:04:03,984 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:03,984 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:03,985 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:03,986 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:03,987 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:03,988 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:03,988 even if it does not contain any `.py` files. 2025-12-16T15:04:03,989 On the other hand, currently there is no concept of package data 2025-12-16T15:04:03,989 directory, all directories are treated like packages. 2025-12-16T15:04:03,990 ******************************************************************************** 2025-12-16T15:04:03,991 !! 2025-12-16T15:04:03,991 check.warn(importable) 2025-12-16T15:04:03,992 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_side_effects' is absent from the `packages` configuration. 2025-12-16T15:04:03,992 !! 2025-12-16T15:04:03,993 ******************************************************************************** 2025-12-16T15:04:03,994 ############################ 2025-12-16T15:04:03,994 # Package would be ignored # 2025-12-16T15:04:03,995 ############################ 2025-12-16T15:04:03,995 Python recognizes 'seal5.transform.detect_side_effects' as an importable package[^1], 2025-12-16T15:04:03,996 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:03,997 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:03,997 package, please make sure that 'seal5.transform.detect_side_effects' is explicitly added 2025-12-16T15:04:03,998 to the `packages` configuration field. 2025-12-16T15:04:03,999 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:03,999 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,000 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,001 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,002 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,003 If you don't want 'seal5.transform.detect_side_effects' to be distributed and are 2025-12-16T15:04:04,004 already explicitly excluding 'seal5.transform.detect_side_effects' via 2025-12-16T15:04:04,004 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,005 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,005 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,007 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,008 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,010 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,010 even if it does not contain any `.py` files. 2025-12-16T15:04:04,011 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,011 directory, all directories are treated like packages. 2025-12-16T15:04:04,012 ******************************************************************************** 2025-12-16T15:04:04,013 !! 2025-12-16T15:04:04,013 check.warn(importable) 2025-12-16T15:04:04,014 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.drop_unused' is absent from the `packages` configuration. 2025-12-16T15:04:04,014 !! 2025-12-16T15:04:04,015 ******************************************************************************** 2025-12-16T15:04:04,016 ############################ 2025-12-16T15:04:04,016 # Package would be ignored # 2025-12-16T15:04:04,017 ############################ 2025-12-16T15:04:04,017 Python recognizes 'seal5.transform.drop_unused' as an importable package[^1], 2025-12-16T15:04:04,018 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,019 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,020 package, please make sure that 'seal5.transform.drop_unused' is explicitly added 2025-12-16T15:04:04,020 to the `packages` configuration field. 2025-12-16T15:04:04,022 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,022 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,023 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,024 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,026 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,027 If you don't want 'seal5.transform.drop_unused' to be distributed and are 2025-12-16T15:04:04,027 already explicitly excluding 'seal5.transform.drop_unused' via 2025-12-16T15:04:04,028 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,029 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,029 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,030 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,032 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,033 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,034 even if it does not contain any `.py` files. 2025-12-16T15:04:04,035 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,035 directory, all directories are treated like packages. 2025-12-16T15:04:04,036 ******************************************************************************** 2025-12-16T15:04:04,037 !! 2025-12-16T15:04:04,038 check.warn(importable) 2025-12-16T15:04:04,038 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.eliminate_mod_rfs' is absent from the `packages` configuration. 2025-12-16T15:04:04,039 !! 2025-12-16T15:04:04,040 ******************************************************************************** 2025-12-16T15:04:04,041 ############################ 2025-12-16T15:04:04,042 # Package would be ignored # 2025-12-16T15:04:04,042 ############################ 2025-12-16T15:04:04,043 Python recognizes 'seal5.transform.eliminate_mod_rfs' as an importable package[^1], 2025-12-16T15:04:04,043 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,044 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,045 package, please make sure that 'seal5.transform.eliminate_mod_rfs' is explicitly added 2025-12-16T15:04:04,045 to the `packages` configuration field. 2025-12-16T15:04:04,047 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,047 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,048 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,049 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,050 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,051 If you don't want 'seal5.transform.eliminate_mod_rfs' to be distributed and are 2025-12-16T15:04:04,052 already explicitly excluding 'seal5.transform.eliminate_mod_rfs' via 2025-12-16T15:04:04,052 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,053 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,053 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,055 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,056 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,057 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,058 even if it does not contain any `.py` files. 2025-12-16T15:04:04,059 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,059 directory, all directories are treated like packages. 2025-12-16T15:04:04,060 ******************************************************************************** 2025-12-16T15:04:04,061 !! 2025-12-16T15:04:04,061 check.warn(importable) 2025-12-16T15:04:04,062 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.eliminate_rd_cmp_zero' is absent from the `packages` configuration. 2025-12-16T15:04:04,063 !! 2025-12-16T15:04:04,064 ******************************************************************************** 2025-12-16T15:04:04,065 ############################ 2025-12-16T15:04:04,065 # Package would be ignored # 2025-12-16T15:04:04,066 ############################ 2025-12-16T15:04:04,067 Python recognizes 'seal5.transform.eliminate_rd_cmp_zero' as an importable package[^1], 2025-12-16T15:04:04,067 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,069 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,069 package, please make sure that 'seal5.transform.eliminate_rd_cmp_zero' is explicitly added 2025-12-16T15:04:04,070 to the `packages` configuration field. 2025-12-16T15:04:04,071 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,072 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,073 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,074 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,075 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,077 If you don't want 'seal5.transform.eliminate_rd_cmp_zero' to be distributed and are 2025-12-16T15:04:04,077 already explicitly excluding 'seal5.transform.eliminate_rd_cmp_zero' via 2025-12-16T15:04:04,078 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,078 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,079 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,080 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,081 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,083 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,084 even if it does not contain any `.py` files. 2025-12-16T15:04:04,084 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,085 directory, all directories are treated like packages. 2025-12-16T15:04:04,085 ******************************************************************************** 2025-12-16T15:04:04,086 !! 2025-12-16T15:04:04,087 check.warn(importable) 2025-12-16T15:04:04,087 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.explicit_truncations' is absent from the `packages` configuration. 2025-12-16T15:04:04,088 !! 2025-12-16T15:04:04,089 ******************************************************************************** 2025-12-16T15:04:04,090 ############################ 2025-12-16T15:04:04,090 # Package would be ignored # 2025-12-16T15:04:04,091 ############################ 2025-12-16T15:04:04,092 Python recognizes 'seal5.transform.explicit_truncations' as an importable package[^1], 2025-12-16T15:04:04,092 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,093 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,094 package, please make sure that 'seal5.transform.explicit_truncations' is explicitly added 2025-12-16T15:04:04,095 to the `packages` configuration field. 2025-12-16T15:04:04,096 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,097 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,097 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,098 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,100 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,101 If you don't want 'seal5.transform.explicit_truncations' to be distributed and are 2025-12-16T15:04:04,102 already explicitly excluding 'seal5.transform.explicit_truncations' via 2025-12-16T15:04:04,102 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,103 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,103 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,104 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,105 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,107 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,107 even if it does not contain any `.py` files. 2025-12-16T15:04:04,108 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,108 directory, all directories are treated like packages. 2025-12-16T15:04:04,109 ******************************************************************************** 2025-12-16T15:04:04,110 !! 2025-12-16T15:04:04,111 check.warn(importable) 2025-12-16T15:04:04,111 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.filter_model' is absent from the `packages` configuration. 2025-12-16T15:04:04,111 !! 2025-12-16T15:04:04,112 ******************************************************************************** 2025-12-16T15:04:04,113 ############################ 2025-12-16T15:04:04,113 # Package would be ignored # 2025-12-16T15:04:04,114 ############################ 2025-12-16T15:04:04,114 Python recognizes 'seal5.transform.filter_model' as an importable package[^1], 2025-12-16T15:04:04,115 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,115 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,116 package, please make sure that 'seal5.transform.filter_model' is explicitly added 2025-12-16T15:04:04,116 to the `packages` configuration field. 2025-12-16T15:04:04,117 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,118 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,118 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,119 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,120 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,121 If you don't want 'seal5.transform.filter_model' to be distributed and are 2025-12-16T15:04:04,122 already explicitly excluding 'seal5.transform.filter_model' via 2025-12-16T15:04:04,122 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,123 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,124 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,125 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,126 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,127 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,128 even if it does not contain any `.py` files. 2025-12-16T15:04:04,130 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,131 directory, all directories are treated like packages. 2025-12-16T15:04:04,131 ******************************************************************************** 2025-12-16T15:04:04,132 !! 2025-12-16T15:04:04,133 check.warn(importable) 2025-12-16T15:04:04,134 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.infer_types' is absent from the `packages` configuration. 2025-12-16T15:04:04,135 !! 2025-12-16T15:04:04,136 ******************************************************************************** 2025-12-16T15:04:04,136 ############################ 2025-12-16T15:04:04,137 # Package would be ignored # 2025-12-16T15:04:04,137 ############################ 2025-12-16T15:04:04,138 Python recognizes 'seal5.transform.infer_types' as an importable package[^1], 2025-12-16T15:04:04,138 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,139 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,140 package, please make sure that 'seal5.transform.infer_types' is explicitly added 2025-12-16T15:04:04,140 to the `packages` configuration field. 2025-12-16T15:04:04,141 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,142 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,142 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,143 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,144 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,145 If you don't want 'seal5.transform.infer_types' to be distributed and are 2025-12-16T15:04:04,146 already explicitly excluding 'seal5.transform.infer_types' via 2025-12-16T15:04:04,146 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,147 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,147 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,148 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,149 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,150 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,151 even if it does not contain any `.py` files. 2025-12-16T15:04:04,152 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,152 directory, all directories are treated like packages. 2025-12-16T15:04:04,153 ******************************************************************************** 2025-12-16T15:04:04,154 !! 2025-12-16T15:04:04,154 check.warn(importable) 2025-12-16T15:04:04,155 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.inline_functions' is absent from the `packages` configuration. 2025-12-16T15:04:04,156 !! 2025-12-16T15:04:04,157 ******************************************************************************** 2025-12-16T15:04:04,157 ############################ 2025-12-16T15:04:04,158 # Package would be ignored # 2025-12-16T15:04:04,158 ############################ 2025-12-16T15:04:04,159 Python recognizes 'seal5.transform.inline_functions' as an importable package[^1], 2025-12-16T15:04:04,159 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,160 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,161 package, please make sure that 'seal5.transform.inline_functions' is explicitly added 2025-12-16T15:04:04,162 to the `packages` configuration field. 2025-12-16T15:04:04,163 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,163 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,164 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,165 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,166 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,167 If you don't want 'seal5.transform.inline_functions' to be distributed and are 2025-12-16T15:04:04,168 already explicitly excluding 'seal5.transform.inline_functions' via 2025-12-16T15:04:04,169 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,169 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,170 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,171 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,172 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,173 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,174 even if it does not contain any `.py` files. 2025-12-16T15:04:04,174 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,175 directory, all directories are treated like packages. 2025-12-16T15:04:04,175 ******************************************************************************** 2025-12-16T15:04:04,176 !! 2025-12-16T15:04:04,176 check.warn(importable) 2025-12-16T15:04:04,177 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.optimize_instructions' is absent from the `packages` configuration. 2025-12-16T15:04:04,177 !! 2025-12-16T15:04:04,178 ******************************************************************************** 2025-12-16T15:04:04,178 ############################ 2025-12-16T15:04:04,179 # Package would be ignored # 2025-12-16T15:04:04,183 ############################ 2025-12-16T15:04:04,183 Python recognizes 'seal5.transform.optimize_instructions' as an importable package[^1], 2025-12-16T15:04:04,184 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,185 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,186 package, please make sure that 'seal5.transform.optimize_instructions' is explicitly added 2025-12-16T15:04:04,186 to the `packages` configuration field. 2025-12-16T15:04:04,187 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,188 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,188 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,189 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,190 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,191 If you don't want 'seal5.transform.optimize_instructions' to be distributed and are 2025-12-16T15:04:04,191 already explicitly excluding 'seal5.transform.optimize_instructions' via 2025-12-16T15:04:04,192 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,192 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,193 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,194 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,195 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,196 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,197 even if it does not contain any `.py` files. 2025-12-16T15:04:04,197 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,198 directory, all directories are treated like packages. 2025-12-16T15:04:04,199 ******************************************************************************** 2025-12-16T15:04:04,200 !! 2025-12-16T15:04:04,200 check.warn(importable) 2025-12-16T15:04:04,201 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.process_settings' is absent from the `packages` configuration. 2025-12-16T15:04:04,201 !! 2025-12-16T15:04:04,203 ******************************************************************************** 2025-12-16T15:04:04,203 ############################ 2025-12-16T15:04:04,204 # Package would be ignored # 2025-12-16T15:04:04,204 ############################ 2025-12-16T15:04:04,205 Python recognizes 'seal5.transform.process_settings' as an importable package[^1], 2025-12-16T15:04:04,205 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,206 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,207 package, please make sure that 'seal5.transform.process_settings' is explicitly added 2025-12-16T15:04:04,207 to the `packages` configuration field. 2025-12-16T15:04:04,208 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,209 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,209 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,210 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,211 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,212 If you don't want 'seal5.transform.process_settings' to be distributed and are 2025-12-16T15:04:04,212 already explicitly excluding 'seal5.transform.process_settings' via 2025-12-16T15:04:04,213 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,213 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,214 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,215 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,216 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,218 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,218 even if it does not contain any `.py` files. 2025-12-16T15:04:04,219 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,219 directory, all directories are treated like packages. 2025-12-16T15:04:04,220 ******************************************************************************** 2025-12-16T15:04:04,221 !! 2025-12-16T15:04:04,221 check.warn(importable) 2025-12-16T15:04:04,222 /tmp/pip-build-env-p_o30ioa/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.simplify_trivial_slices' is absent from the `packages` configuration. 2025-12-16T15:04:04,222 !! 2025-12-16T15:04:04,224 ******************************************************************************** 2025-12-16T15:04:04,224 ############################ 2025-12-16T15:04:04,225 # Package would be ignored # 2025-12-16T15:04:04,225 ############################ 2025-12-16T15:04:04,226 Python recognizes 'seal5.transform.simplify_trivial_slices' as an importable package[^1], 2025-12-16T15:04:04,226 but it is absent from setuptools' `packages` configuration. 2025-12-16T15:04:04,227 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-16T15:04:04,228 package, please make sure that 'seal5.transform.simplify_trivial_slices' is explicitly added 2025-12-16T15:04:04,228 to the `packages` configuration field. 2025-12-16T15:04:04,229 Alternatively, you can also rely on setuptools' discovery methods 2025-12-16T15:04:04,230 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-16T15:04:04,230 instead of `find_packages(...)`/`find:`). 2025-12-16T15:04:04,231 You can read more about "package discovery" on setuptools documentation page: 2025-12-16T15:04:04,232 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-16T15:04:04,233 If you don't want 'seal5.transform.simplify_trivial_slices' to be distributed and are 2025-12-16T15:04:04,234 already explicitly excluding 'seal5.transform.simplify_trivial_slices' via 2025-12-16T15:04:04,234 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-16T15:04:04,235 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-16T15:04:04,235 combination with a more fine grained `package-data` configuration. 2025-12-16T15:04:04,236 You can read more about "package data files" on setuptools documentation page: 2025-12-16T15:04:04,237 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-16T15:04:04,238 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-16T15:04:04,239 even if it does not contain any `.py` files. 2025-12-16T15:04:04,239 On the other hand, currently there is no concept of package data 2025-12-16T15:04:04,240 directory, all directories are treated like packages. 2025-12-16T15:04:04,240 ******************************************************************************** 2025-12-16T15:04:04,241 !! 2025-12-16T15:04:04,242 check.warn(importable) 2025-12-16T15:04:04,242 creating build/lib/seal5/backends 2025-12-16T15:04:04,243 copying seal5/backends/__init__.py -> build/lib/seal5/backends 2025-12-16T15:04:04,244 creating build/lib/seal5/backends/coredsl2 2025-12-16T15:04:04,244 copying seal5/backends/coredsl2/__init__.py -> build/lib/seal5/backends/coredsl2 2025-12-16T15:04:04,244 copying seal5/backends/coredsl2/visitor.py -> build/lib/seal5/backends/coredsl2 2025-12-16T15:04:04,245 copying seal5/backends/coredsl2/writer.py -> build/lib/seal5/backends/coredsl2 2025-12-16T15:04:04,245 creating build/lib/seal5/backends/llvmir 2025-12-16T15:04:04,246 copying seal5/backends/llvmir/__init__.py -> build/lib/seal5/backends/llvmir 2025-12-16T15:04:04,247 copying seal5/backends/llvmir/writer.py -> build/lib/seal5/backends/llvmir 2025-12-16T15:04:04,247 creating build/lib/seal5/backends/patterngen 2025-12-16T15:04:04,248 copying seal5/backends/patterngen/__init__.py -> build/lib/seal5/backends/patterngen 2025-12-16T15:04:04,248 copying seal5/backends/patterngen/writer.py -> build/lib/seal5/backends/patterngen 2025-12-16T15:04:04,249 creating build/lib/seal5/backends/report 2025-12-16T15:04:04,249 copying seal5/backends/report/__init__.py -> build/lib/seal5/backends/report 2025-12-16T15:04:04,250 creating build/lib/seal5/backends/report/diff 2025-12-16T15:04:04,250 copying seal5/backends/report/diff/__init__.py -> build/lib/seal5/backends/report/diff 2025-12-16T15:04:04,251 copying seal5/backends/report/diff/writer.py -> build/lib/seal5/backends/report/diff 2025-12-16T15:04:04,251 creating build/lib/seal5/backends/report/pattern_gen 2025-12-16T15:04:04,252 copying seal5/backends/report/pattern_gen/__init__.py -> build/lib/seal5/backends/report/pattern_gen 2025-12-16T15:04:04,253 copying seal5/backends/report/pattern_gen/writer.py -> build/lib/seal5/backends/report/pattern_gen 2025-12-16T15:04:04,253 creating build/lib/seal5/backends/report/properties 2025-12-16T15:04:04,253 copying seal5/backends/report/properties/__init__.py -> build/lib/seal5/backends/report/properties 2025-12-16T15:04:04,254 copying seal5/backends/report/properties/writer.py -> build/lib/seal5/backends/report/properties 2025-12-16T15:04:04,254 creating build/lib/seal5/backends/report/status 2025-12-16T15:04:04,255 copying seal5/backends/report/status/__init__.py -> build/lib/seal5/backends/report/status 2025-12-16T15:04:04,256 copying seal5/backends/report/status/writer.py -> build/lib/seal5/backends/report/status 2025-12-16T15:04:04,256 creating build/lib/seal5/backends/report/test_results 2025-12-16T15:04:04,257 copying seal5/backends/report/test_results/__init__.py -> build/lib/seal5/backends/report/test_results 2025-12-16T15:04:04,257 copying seal5/backends/report/test_results/writer.py -> build/lib/seal5/backends/report/test_results 2025-12-16T15:04:04,258 creating build/lib/seal5/backends/report/times 2025-12-16T15:04:04,258 copying seal5/backends/report/times/__init__.py -> build/lib/seal5/backends/report/times 2025-12-16T15:04:04,259 copying seal5/backends/report/times/writer.py -> build/lib/seal5/backends/report/times 2025-12-16T15:04:04,259 creating build/lib/seal5/backends/riscv_features 2025-12-16T15:04:04,260 copying seal5/backends/riscv_features/__init__.py -> build/lib/seal5/backends/riscv_features 2025-12-16T15:04:04,260 copying seal5/backends/riscv_features/writer.py -> build/lib/seal5/backends/riscv_features 2025-12-16T15:04:04,261 creating build/lib/seal5/backends/riscv_features/templates 2025-12-16T15:04:04,261 copying seal5/backends/riscv_features/templates/__init__.py -> build/lib/seal5/backends/riscv_features/templates 2025-12-16T15:04:04,262 copying seal5/backends/riscv_features/templates/riscv_features.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-16T15:04:04,262 copying seal5/backends/riscv_features/templates/riscv_features_experimental_new.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-16T15:04:04,263 copying seal5/backends/riscv_features/templates/riscv_features_experimental_new_slim.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-16T15:04:04,263 copying seal5/backends/riscv_features/templates/riscv_features_new.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-16T15:04:04,264 copying seal5/backends/riscv_features/templates/riscv_features_new_slim.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-16T15:04:04,264 copying seal5/backends/riscv_features/templates/test_riscv_attributes.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-16T15:04:04,265 creating build/lib/seal5/backends/riscv_field_types 2025-12-16T15:04:04,265 copying seal5/backends/riscv_field_types/__init__.py -> build/lib/seal5/backends/riscv_field_types 2025-12-16T15:04:04,266 copying seal5/backends/riscv_field_types/writer.py -> build/lib/seal5/backends/riscv_field_types 2025-12-16T15:04:04,266 creating build/lib/seal5/backends/riscv_gisel_legalizer 2025-12-16T15:04:04,267 copying seal5/backends/riscv_gisel_legalizer/__init__.py -> build/lib/seal5/backends/riscv_gisel_legalizer 2025-12-16T15:04:04,267 copying seal5/backends/riscv_gisel_legalizer/writer.py -> build/lib/seal5/backends/riscv_gisel_legalizer 2025-12-16T15:04:04,268 creating build/lib/seal5/backends/riscv_instr_info 2025-12-16T15:04:04,268 copying seal5/backends/riscv_instr_info/__init__.py -> build/lib/seal5/backends/riscv_instr_info 2025-12-16T15:04:04,269 copying seal5/backends/riscv_instr_info/writer.py -> build/lib/seal5/backends/riscv_instr_info 2025-12-16T15:04:04,269 creating build/lib/seal5/backends/riscv_instr_info/templates 2025-12-16T15:04:04,270 copying seal5/backends/riscv_instr_info/templates/__init__.py -> build/lib/seal5/backends/riscv_instr_info/templates 2025-12-16T15:04:04,271 copying seal5/backends/riscv_instr_info/templates/instr_tablegen.mako -> build/lib/seal5/backends/riscv_instr_info/templates 2025-12-16T15:04:04,271 creating build/lib/seal5/backends/riscv_intrinsics 2025-12-16T15:04:04,272 copying seal5/backends/riscv_intrinsics/__init__.py -> build/lib/seal5/backends/riscv_intrinsics 2025-12-16T15:04:04,272 copying seal5/backends/riscv_intrinsics/writer.py -> build/lib/seal5/backends/riscv_intrinsics 2025-12-16T15:04:04,273 creating build/lib/seal5/backends/riscv_isa_info 2025-12-16T15:04:04,273 copying seal5/backends/riscv_isa_info/__init__.py -> build/lib/seal5/backends/riscv_isa_info 2025-12-16T15:04:04,274 copying seal5/backends/riscv_isa_info/writer.py -> build/lib/seal5/backends/riscv_isa_info 2025-12-16T15:04:04,274 creating build/lib/seal5/backends/riscv_register_info 2025-12-16T15:04:04,275 copying seal5/backends/riscv_register_info/__init__.py -> build/lib/seal5/backends/riscv_register_info 2025-12-16T15:04:04,276 copying seal5/backends/riscv_register_info/writer.py -> build/lib/seal5/backends/riscv_register_info 2025-12-16T15:04:04,276 creating build/lib/seal5/backends/viewer_seal5 2025-12-16T15:04:04,276 copying seal5/backends/viewer_seal5/__init__.py -> build/lib/seal5/backends/viewer_seal5 2025-12-16T15:04:04,277 copying seal5/backends/viewer_seal5/treegen.py -> build/lib/seal5/backends/viewer_seal5 2025-12-16T15:04:04,277 copying seal5/backends/viewer_seal5/utils.py -> build/lib/seal5/backends/viewer_seal5 2025-12-16T15:04:04,278 copying seal5/backends/viewer_seal5/viewer.py -> build/lib/seal5/backends/viewer_seal5 2025-12-16T15:04:04,278 creating build/lib/seal5/backends/yaml 2025-12-16T15:04:04,279 copying seal5/backends/yaml/__init__.py -> build/lib/seal5/backends/yaml 2025-12-16T15:04:04,279 copying seal5/backends/yaml/writer.py -> build/lib/seal5/backends/yaml 2025-12-16T15:04:04,280 creating build/lib/seal5/cli 2025-12-16T15:04:04,280 copying seal5/cli/__init__.py -> build/lib/seal5/cli 2025-12-16T15:04:04,281 copying seal5/cli/build.py -> build/lib/seal5/cli 2025-12-16T15:04:04,281 copying seal5/cli/clean.py -> build/lib/seal5/cli 2025-12-16T15:04:04,282 copying seal5/cli/common.py -> build/lib/seal5/cli 2025-12-16T15:04:04,283 copying seal5/cli/deploy.py -> build/lib/seal5/cli 2025-12-16T15:04:04,283 copying seal5/cli/export.py -> build/lib/seal5/cli 2025-12-16T15:04:04,284 copying seal5/cli/generate.py -> build/lib/seal5/cli 2025-12-16T15:04:04,284 copying seal5/cli/init.py -> build/lib/seal5/cli 2025-12-16T15:04:04,284 copying seal5/cli/install.py -> build/lib/seal5/cli 2025-12-16T15:04:04,285 copying seal5/cli/load.py -> build/lib/seal5/cli 2025-12-16T15:04:04,286 copying seal5/cli/main.py -> build/lib/seal5/cli 2025-12-16T15:04:04,286 copying seal5/cli/patch.py -> build/lib/seal5/cli 2025-12-16T15:04:04,287 copying seal5/cli/reset.py -> build/lib/seal5/cli 2025-12-16T15:04:04,287 copying seal5/cli/setup.py -> build/lib/seal5/cli 2025-12-16T15:04:04,288 copying seal5/cli/test.py -> build/lib/seal5/cli 2025-12-16T15:04:04,288 copying seal5/cli/transform.py -> build/lib/seal5/cli 2025-12-16T15:04:04,289 copying seal5/cli/wrapper.py -> build/lib/seal5/cli 2025-12-16T15:04:04,289 creating build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,290 copying seal5/frontends/coredsl2_seal5/.gitignore -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,290 copying seal5/frontends/coredsl2_seal5/CoreDSL2.g4 -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,291 copying seal5/frontends/coredsl2_seal5/README.md -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,291 copying seal5/frontends/coredsl2_seal5/__init__.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,292 copying seal5/frontends/coredsl2_seal5/antlr.sh -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,292 copying seal5/frontends/coredsl2_seal5/architecture_model_builder.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,293 copying seal5/frontends/coredsl2_seal5/behavior_model_builder.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,293 copying seal5/frontends/coredsl2_seal5/expr_interpreter.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,294 copying seal5/frontends/coredsl2_seal5/importer.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,294 copying seal5/frontends/coredsl2_seal5/load_order.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,295 copying seal5/frontends/coredsl2_seal5/parser.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,296 copying seal5/frontends/coredsl2_seal5/utils.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,296 creating build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,297 copying seal5/frontends/coredsl2_seal5/parser_gen/.gitignore -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,297 copying seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Lexer.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,298 copying seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Listener.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,298 copying seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Parser.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,299 copying seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Visitor.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,299 copying seal5/frontends/coredsl2_seal5/parser_gen/__init__.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,299 creating build/lib/seal5/resources 2025-12-16T15:04:04,300 copying seal5/resources/__init__.py -> build/lib/seal5/resources 2025-12-16T15:04:04,300 copying seal5/resources/lit.cfg.py -> build/lib/seal5/resources 2025-12-16T15:04:04,301 copying seal5/resources/resources.py -> build/lib/seal5/resources 2025-12-16T15:04:04,301 creating build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,302 copying seal5/resources/patches/llvm/github_ci.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,302 copying seal5/resources/patches/llvm/gitignore.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,303 copying seal5/resources/patches/llvm/gitlab_ci.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,303 copying seal5/resources/patches/llvm/insert_markers_llvm17.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,304 copying seal5/resources/patches/llvm/insert_markers_llvm18.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,304 copying seal5/resources/patches/llvm/insert_markers_llvm19.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,305 copying seal5/resources/patches/llvm/insert_markers_llvm20.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,305 copying seal5/resources/patches/llvm/insert_markers_llvm21.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,306 copying seal5/resources/patches/llvm/legalizer_fix_1.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,306 copying seal5/resources/patches/llvm/legalizer_fix_2.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,307 copying seal5/resources/patches/llvm/legalizer_split.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,307 copying seal5/resources/patches/llvm/regclass_gpr32v.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,308 copying seal5/resources/patches/llvm/simd_gpr32v.patch -> build/lib/seal5/resources/patches/llvm 2025-12-16T15:04:04,308 creating build/lib/seal5/tools 2025-12-16T15:04:04,309 copying seal5/tools/__init__.py -> build/lib/seal5/tools 2025-12-16T15:04:04,309 copying seal5/tools/cdsl2llvm.py -> build/lib/seal5/tools 2025-12-16T15:04:04,310 copying seal5/tools/cmake.py -> build/lib/seal5/tools 2025-12-16T15:04:04,310 copying seal5/tools/git.py -> build/lib/seal5/tools 2025-12-16T15:04:04,311 copying seal5/tools/inject_patches.py -> build/lib/seal5/tools 2025-12-16T15:04:04,312 copying seal5/tools/llvm.py -> build/lib/seal5/tools 2025-12-16T15:04:04,312 copying seal5/tools/m2isar.py -> build/lib/seal5/tools 2025-12-16T15:04:04,313 creating build/lib/seal5/transform 2025-12-16T15:04:04,313 copying seal5/transform/__init__.py -> build/lib/seal5/transform 2025-12-16T15:04:04,314 copying seal5/transform/converter.py -> build/lib/seal5/transform 2025-12-16T15:04:04,314 creating build/lib/seal5/transform/annotate_opcodes 2025-12-16T15:04:04,315 copying seal5/transform/annotate_opcodes/__init__.py -> build/lib/seal5/transform/annotate_opcodes 2025-12-16T15:04:04,315 copying seal5/transform/annotate_opcodes/annotate.py -> build/lib/seal5/transform/annotate_opcodes 2025-12-16T15:04:04,316 creating build/lib/seal5/transform/check_pattern_support 2025-12-16T15:04:04,316 copying seal5/transform/check_pattern_support/__init__.py -> build/lib/seal5/transform/check_pattern_support 2025-12-16T15:04:04,317 copying seal5/transform/check_pattern_support/check.py -> build/lib/seal5/transform/check_pattern_support 2025-12-16T15:04:04,317 creating build/lib/seal5/transform/collect_immediate_operands 2025-12-16T15:04:04,318 copying seal5/transform/collect_immediate_operands/__init__.py -> build/lib/seal5/transform/collect_immediate_operands 2025-12-16T15:04:04,318 copying seal5/transform/collect_immediate_operands/collect.py -> build/lib/seal5/transform/collect_immediate_operands 2025-12-16T15:04:04,319 copying seal5/transform/collect_immediate_operands/visitor.py -> build/lib/seal5/transform/collect_immediate_operands 2025-12-16T15:04:04,319 creating build/lib/seal5/transform/collect_operand_types 2025-12-16T15:04:04,320 copying seal5/transform/collect_operand_types/__init__.py -> build/lib/seal5/transform/collect_operand_types 2025-12-16T15:04:04,320 copying seal5/transform/collect_operand_types/collect.py -> build/lib/seal5/transform/collect_operand_types 2025-12-16T15:04:04,321 copying seal5/transform/collect_operand_types/visitor.py -> build/lib/seal5/transform/collect_operand_types 2025-12-16T15:04:04,321 creating build/lib/seal5/transform/collect_raises 2025-12-16T15:04:04,322 copying seal5/transform/collect_raises/__init__.py -> build/lib/seal5/transform/collect_raises 2025-12-16T15:04:04,322 copying seal5/transform/collect_raises/collect.py -> build/lib/seal5/transform/collect_raises 2025-12-16T15:04:04,323 copying seal5/transform/collect_raises/visitor.py -> build/lib/seal5/transform/collect_raises 2025-12-16T15:04:04,323 creating build/lib/seal5/transform/collect_register_operands 2025-12-16T15:04:04,324 copying seal5/transform/collect_register_operands/__init__.py -> build/lib/seal5/transform/collect_register_operands 2025-12-16T15:04:04,324 copying seal5/transform/collect_register_operands/collect.py -> build/lib/seal5/transform/collect_register_operands 2025-12-16T15:04:04,325 copying seal5/transform/collect_register_operands/visitor.py -> build/lib/seal5/transform/collect_register_operands 2025-12-16T15:04:04,325 creating build/lib/seal5/transform/detect_calls 2025-12-16T15:04:04,326 copying seal5/transform/detect_calls/__init__.py -> build/lib/seal5/transform/detect_calls 2025-12-16T15:04:04,326 copying seal5/transform/detect_calls/collect.py -> build/lib/seal5/transform/detect_calls 2025-12-16T15:04:04,327 copying seal5/transform/detect_calls/visitor.py -> build/lib/seal5/transform/detect_calls 2025-12-16T15:04:04,327 creating build/lib/seal5/transform/detect_imm_leafs 2025-12-16T15:04:04,328 copying seal5/transform/detect_imm_leafs/__init__.py -> build/lib/seal5/transform/detect_imm_leafs 2025-12-16T15:04:04,328 copying seal5/transform/detect_imm_leafs/collect.py -> build/lib/seal5/transform/detect_imm_leafs 2025-12-16T15:04:04,329 copying seal5/transform/detect_imm_leafs/visitor.py -> build/lib/seal5/transform/detect_imm_leafs 2025-12-16T15:04:04,329 creating build/lib/seal5/transform/detect_inouts 2025-12-16T15:04:04,330 copying seal5/transform/detect_inouts/__init__.py -> build/lib/seal5/transform/detect_inouts 2025-12-16T15:04:04,330 copying seal5/transform/detect_inouts/collect.py -> build/lib/seal5/transform/detect_inouts 2025-12-16T15:04:04,331 copying seal5/transform/detect_inouts/utils.py -> build/lib/seal5/transform/detect_inouts 2025-12-16T15:04:04,331 copying seal5/transform/detect_inouts/visitor.py -> build/lib/seal5/transform/detect_inouts 2025-12-16T15:04:04,332 creating build/lib/seal5/transform/detect_loops 2025-12-16T15:04:04,332 copying seal5/transform/detect_loops/__init__.py -> build/lib/seal5/transform/detect_loops 2025-12-16T15:04:04,333 copying seal5/transform/detect_loops/collect.py -> build/lib/seal5/transform/detect_loops 2025-12-16T15:04:04,333 copying seal5/transform/detect_loops/visitor.py -> build/lib/seal5/transform/detect_loops 2025-12-16T15:04:04,334 creating build/lib/seal5/transform/detect_registers 2025-12-16T15:04:04,335 copying seal5/transform/detect_registers/__init__.py -> build/lib/seal5/transform/detect_registers 2025-12-16T15:04:04,335 copying seal5/transform/detect_registers/detect.py -> build/lib/seal5/transform/detect_registers 2025-12-16T15:04:04,335 creating build/lib/seal5/transform/detect_side_effects 2025-12-16T15:04:04,336 copying seal5/transform/detect_side_effects/__init__.py -> build/lib/seal5/transform/detect_side_effects 2025-12-16T15:04:04,336 copying seal5/transform/detect_side_effects/collect.py -> build/lib/seal5/transform/detect_side_effects 2025-12-16T15:04:04,337 copying seal5/transform/detect_side_effects/visitor.py -> build/lib/seal5/transform/detect_side_effects 2025-12-16T15:04:04,337 creating build/lib/seal5/transform/drop_unused 2025-12-16T15:04:04,338 copying seal5/transform/drop_unused/__init__.py -> build/lib/seal5/transform/drop_unused 2025-12-16T15:04:04,338 copying seal5/transform/drop_unused/optimizer.py -> build/lib/seal5/transform/drop_unused 2025-12-16T15:04:04,339 copying seal5/transform/drop_unused/track_uses.py -> build/lib/seal5/transform/drop_unused 2025-12-16T15:04:04,339 creating build/lib/seal5/transform/eliminate_mod_rfs 2025-12-16T15:04:04,340 copying seal5/transform/eliminate_mod_rfs/__init__.py -> build/lib/seal5/transform/eliminate_mod_rfs 2025-12-16T15:04:04,340 copying seal5/transform/eliminate_mod_rfs/transform.py -> build/lib/seal5/transform/eliminate_mod_rfs 2025-12-16T15:04:04,341 copying seal5/transform/eliminate_mod_rfs/visitor.py -> build/lib/seal5/transform/eliminate_mod_rfs 2025-12-16T15:04:04,341 creating build/lib/seal5/transform/eliminate_rd_cmp_zero 2025-12-16T15:04:04,342 copying seal5/transform/eliminate_rd_cmp_zero/__init__.py -> build/lib/seal5/transform/eliminate_rd_cmp_zero 2025-12-16T15:04:04,342 copying seal5/transform/eliminate_rd_cmp_zero/transform.py -> build/lib/seal5/transform/eliminate_rd_cmp_zero 2025-12-16T15:04:04,344 copying seal5/transform/eliminate_rd_cmp_zero/visitor.py -> build/lib/seal5/transform/eliminate_rd_cmp_zero 2025-12-16T15:04:04,346 creating build/lib/seal5/transform/explicit_truncations 2025-12-16T15:04:04,347 copying seal5/transform/explicit_truncations/__init__.py -> build/lib/seal5/transform/explicit_truncations 2025-12-16T15:04:04,349 copying seal5/transform/explicit_truncations/transform.py -> build/lib/seal5/transform/explicit_truncations 2025-12-16T15:04:04,351 copying seal5/transform/explicit_truncations/visitor.py -> build/lib/seal5/transform/explicit_truncations 2025-12-16T15:04:04,354 creating build/lib/seal5/transform/filter_model 2025-12-16T15:04:04,355 copying seal5/transform/filter_model/__init__.py -> build/lib/seal5/transform/filter_model 2025-12-16T15:04:04,358 copying seal5/transform/filter_model/filter.py -> build/lib/seal5/transform/filter_model 2025-12-16T15:04:04,360 creating build/lib/seal5/transform/infer_types 2025-12-16T15:04:04,362 copying seal5/transform/infer_types/__init__.py -> build/lib/seal5/transform/infer_types 2025-12-16T15:04:04,364 copying seal5/transform/infer_types/transform.py -> build/lib/seal5/transform/infer_types 2025-12-16T15:04:04,366 copying seal5/transform/infer_types/visitor.py -> build/lib/seal5/transform/infer_types 2025-12-16T15:04:04,369 creating build/lib/seal5/transform/inline_functions 2025-12-16T15:04:04,370 copying seal5/transform/inline_functions/__init__.py -> build/lib/seal5/transform/inline_functions 2025-12-16T15:04:04,373 copying seal5/transform/inline_functions/optimizer.py -> build/lib/seal5/transform/inline_functions 2025-12-16T15:04:04,375 copying seal5/transform/inline_functions/visitor.py -> build/lib/seal5/transform/inline_functions 2025-12-16T15:04:04,377 creating build/lib/seal5/transform/optimize_instructions 2025-12-16T15:04:04,378 copying seal5/transform/optimize_instructions/__init__.py -> build/lib/seal5/transform/optimize_instructions 2025-12-16T15:04:04,381 copying seal5/transform/optimize_instructions/optimizer.py -> build/lib/seal5/transform/optimize_instructions 2025-12-16T15:04:04,383 creating build/lib/seal5/transform/process_settings 2025-12-16T15:04:04,384 copying seal5/transform/process_settings/__init__.py -> build/lib/seal5/transform/process_settings 2025-12-16T15:04:04,386 copying seal5/transform/process_settings/transform.py -> build/lib/seal5/transform/process_settings 2025-12-16T15:04:04,388 creating build/lib/seal5/transform/simplify_trivial_slices 2025-12-16T15:04:04,389 copying seal5/transform/simplify_trivial_slices/__init__.py -> build/lib/seal5/transform/simplify_trivial_slices 2025-12-16T15:04:04,392 copying seal5/transform/simplify_trivial_slices/transform.py -> build/lib/seal5/transform/simplify_trivial_slices 2025-12-16T15:04:04,394 copying seal5/transform/simplify_trivial_slices/visitor.py -> build/lib/seal5/transform/simplify_trivial_slices 2025-12-16T15:04:04,411 installing to build/bdist.linux-armv7l/wheel 2025-12-16T15:04:04,411 running install 2025-12-16T15:04:04,435 running install_lib 2025-12-16T15:04:04,443 creating build/bdist.linux-armv7l/wheel 2025-12-16T15:04:04,446 creating build/bdist.linux-armv7l/wheel/seal5 2025-12-16T15:04:04,447 copying build/lib/seal5/flow.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,450 copying build/lib/seal5/model.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,453 copying build/lib/seal5/dependencies.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,455 copying build/lib/seal5/types.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,458 creating build/bdist.linux-armv7l/wheel/seal5/tools 2025-12-16T15:04:04,459 copying build/lib/seal5/tools/llvm.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-16T15:04:04,461 copying build/lib/seal5/tools/m2isar.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-16T15:04:04,463 copying build/lib/seal5/tools/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-16T15:04:04,465 copying build/lib/seal5/tools/git.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-16T15:04:04,467 copying build/lib/seal5/tools/inject_patches.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-16T15:04:04,470 copying build/lib/seal5/tools/cmake.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-16T15:04:04,472 copying build/lib/seal5/tools/cdsl2llvm.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-16T15:04:04,474 copying build/lib/seal5/utils.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,476 copying build/lib/seal5/build_cache.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,478 copying build/lib/seal5/passes.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,481 copying build/lib/seal5/metrics.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,483 copying build/lib/seal5/settings.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,485 copying build/lib/seal5/version.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,488 creating build/bdist.linux-armv7l/wheel/seal5/frontends 2025-12-16T15:04:04,490 creating build/bdist.linux-armv7l/wheel/seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,491 copying build/lib/seal5/frontends/coredsl2_seal5/load_order.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,493 copying build/lib/seal5/frontends/coredsl2_seal5/.gitignore -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,495 copying build/lib/seal5/frontends/coredsl2_seal5/importer.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,497 copying build/lib/seal5/frontends/coredsl2_seal5/architecture_model_builder.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,500 copying build/lib/seal5/frontends/coredsl2_seal5/CoreDSL2.g4 -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,502 copying build/lib/seal5/frontends/coredsl2_seal5/utils.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,504 copying build/lib/seal5/frontends/coredsl2_seal5/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,506 copying build/lib/seal5/frontends/coredsl2_seal5/expr_interpreter.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,508 copying build/lib/seal5/frontends/coredsl2_seal5/behavior_model_builder.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,510 copying build/lib/seal5/frontends/coredsl2_seal5/antlr.sh -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,512 copying build/lib/seal5/frontends/coredsl2_seal5/README.md -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,516 creating build/bdist.linux-armv7l/wheel/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,518 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,521 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/.gitignore -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,523 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Parser.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,529 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,531 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Listener.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,534 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Lexer.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-16T15:04:04,537 copying build/lib/seal5/frontends/coredsl2_seal5/parser.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-16T15:04:04,541 creating build/bdist.linux-armv7l/wheel/seal5/resources 2025-12-16T15:04:04,542 copying build/lib/seal5/resources/lit.cfg.py -> build/bdist.linux-armv7l/wheel/./seal5/resources 2025-12-16T15:04:04,544 creating build/bdist.linux-armv7l/wheel/seal5/resources/patches 2025-12-16T15:04:04,546 creating build/bdist.linux-armv7l/wheel/seal5/resources/patches/llvm 2025-12-16T15:04:04,547 copying build/lib/seal5/resources/patches/llvm/insert_markers_llvm19.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,550 copying build/lib/seal5/resources/patches/llvm/insert_markers_llvm21.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,552 copying build/lib/seal5/resources/patches/llvm/simd_gpr32v.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,554 copying build/lib/seal5/resources/patches/llvm/insert_markers_llvm20.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,557 copying build/lib/seal5/resources/patches/llvm/insert_markers_llvm18.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,559 copying build/lib/seal5/resources/patches/llvm/legalizer_fix_1.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,561 copying build/lib/seal5/resources/patches/llvm/legalizer_fix_2.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,563 copying build/lib/seal5/resources/patches/llvm/github_ci.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,565 copying build/lib/seal5/resources/patches/llvm/gitignore.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,567 copying build/lib/seal5/resources/patches/llvm/legalizer_split.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,569 copying build/lib/seal5/resources/patches/llvm/regclass_gpr32v.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,571 copying build/lib/seal5/resources/patches/llvm/gitlab_ci.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,573 copying build/lib/seal5/resources/patches/llvm/insert_markers_llvm17.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-16T15:04:04,575 copying build/lib/seal5/resources/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/resources 2025-12-16T15:04:04,577 copying build/lib/seal5/resources/resources.py -> build/bdist.linux-armv7l/wheel/./seal5/resources 2025-12-16T15:04:04,579 copying build/lib/seal5/index.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,581 copying build/lib/seal5/wrapper.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,583 copying build/lib/seal5/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,585 copying build/lib/seal5/riscv_utils.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,587 copying build/lib/seal5/logging.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,590 creating build/bdist.linux-armv7l/wheel/seal5/cli 2025-12-16T15:04:04,591 copying build/lib/seal5/cli/main.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,593 copying build/lib/seal5/cli/clean.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,595 copying build/lib/seal5/cli/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,597 copying build/lib/seal5/cli/common.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,598 copying build/lib/seal5/cli/generate.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,600 copying build/lib/seal5/cli/deploy.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,602 copying build/lib/seal5/cli/patch.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,604 copying build/lib/seal5/cli/export.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,606 copying build/lib/seal5/cli/install.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,608 copying build/lib/seal5/cli/wrapper.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,610 copying build/lib/seal5/cli/setup.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,612 copying build/lib/seal5/cli/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,613 copying build/lib/seal5/cli/load.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,615 copying build/lib/seal5/cli/build.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,617 copying build/lib/seal5/cli/reset.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,619 copying build/lib/seal5/cli/init.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,621 copying build/lib/seal5/cli/test.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-16T15:04:04,623 copying build/lib/seal5/pass_list.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,626 copying build/lib/seal5/testgen_utils.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,628 copying build/lib/seal5/model_utils.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-16T15:04:04,631 creating build/bdist.linux-armv7l/wheel/seal5/backends 2025-12-16T15:04:04,632 creating build/bdist.linux-armv7l/wheel/seal5/backends/patterngen 2025-12-16T15:04:04,633 copying build/lib/seal5/backends/patterngen/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/patterngen 2025-12-16T15:04:04,635 copying build/lib/seal5/backends/patterngen/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/patterngen 2025-12-16T15:04:04,638 creating build/bdist.linux-armv7l/wheel/seal5/backends/yaml 2025-12-16T15:04:04,639 copying build/lib/seal5/backends/yaml/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/yaml 2025-12-16T15:04:04,641 copying build/lib/seal5/backends/yaml/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/yaml 2025-12-16T15:04:04,644 creating build/bdist.linux-armv7l/wheel/seal5/backends/report 2025-12-16T15:04:04,645 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/status 2025-12-16T15:04:04,646 copying build/lib/seal5/backends/report/status/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/status 2025-12-16T15:04:04,648 copying build/lib/seal5/backends/report/status/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/status 2025-12-16T15:04:04,651 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/diff 2025-12-16T15:04:04,652 copying build/lib/seal5/backends/report/diff/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/diff 2025-12-16T15:04:04,654 copying build/lib/seal5/backends/report/diff/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/diff 2025-12-16T15:04:04,657 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/times 2025-12-16T15:04:04,658 copying build/lib/seal5/backends/report/times/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/times 2025-12-16T15:04:04,659 copying build/lib/seal5/backends/report/times/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/times 2025-12-16T15:04:04,662 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/pattern_gen 2025-12-16T15:04:04,663 copying build/lib/seal5/backends/report/pattern_gen/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/pattern_gen 2025-12-16T15:04:04,665 copying build/lib/seal5/backends/report/pattern_gen/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/pattern_gen 2025-12-16T15:04:04,667 copying build/lib/seal5/backends/report/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report 2025-12-16T15:04:04,669 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/test_results 2025-12-16T15:04:04,670 copying build/lib/seal5/backends/report/test_results/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/test_results 2025-12-16T15:04:04,672 copying build/lib/seal5/backends/report/test_results/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/test_results 2025-12-16T15:04:04,675 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/properties 2025-12-16T15:04:04,676 copying build/lib/seal5/backends/report/properties/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/properties 2025-12-16T15:04:04,678 copying build/lib/seal5/backends/report/properties/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/properties 2025-12-16T15:04:04,681 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_features 2025-12-16T15:04:04,683 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_features/templates 2025-12-16T15:04:04,684 copying build/lib/seal5/backends/riscv_features/templates/riscv_features_new_slim.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-16T15:04:04,686 copying build/lib/seal5/backends/riscv_features/templates/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-16T15:04:04,688 copying build/lib/seal5/backends/riscv_features/templates/test_riscv_attributes.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-16T15:04:04,689 copying build/lib/seal5/backends/riscv_features/templates/riscv_features_experimental_new_slim.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-16T15:04:04,691 copying build/lib/seal5/backends/riscv_features/templates/riscv_features_experimental_new.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-16T15:04:04,693 copying build/lib/seal5/backends/riscv_features/templates/riscv_features.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-16T15:04:04,695 copying build/lib/seal5/backends/riscv_features/templates/riscv_features_new.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-16T15:04:04,697 copying build/lib/seal5/backends/riscv_features/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features 2025-12-16T15:04:04,699 copying build/lib/seal5/backends/riscv_features/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features 2025-12-16T15:04:04,701 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_instr_info 2025-12-16T15:04:04,703 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_instr_info/templates 2025-12-16T15:04:04,704 copying build/lib/seal5/backends/riscv_instr_info/templates/instr_tablegen.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_instr_info/templates 2025-12-16T15:04:04,706 copying build/lib/seal5/backends/riscv_instr_info/templates/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_instr_info/templates 2025-12-16T15:04:04,708 copying build/lib/seal5/backends/riscv_instr_info/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_instr_info 2025-12-16T15:04:04,710 copying build/lib/seal5/backends/riscv_instr_info/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_instr_info 2025-12-16T15:04:04,713 creating build/bdist.linux-armv7l/wheel/seal5/backends/coredsl2 2025-12-16T15:04:04,714 copying build/lib/seal5/backends/coredsl2/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/coredsl2 2025-12-16T15:04:04,716 copying build/lib/seal5/backends/coredsl2/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/coredsl2 2025-12-16T15:04:04,718 copying build/lib/seal5/backends/coredsl2/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/coredsl2 2025-12-16T15:04:04,721 creating build/bdist.linux-armv7l/wheel/seal5/backends/llvmir 2025-12-16T15:04:04,722 copying build/lib/seal5/backends/llvmir/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/llvmir 2025-12-16T15:04:04,724 copying build/lib/seal5/backends/llvmir/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/llvmir 2025-12-16T15:04:04,727 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_register_info 2025-12-16T15:04:04,728 copying build/lib/seal5/backends/riscv_register_info/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_register_info 2025-12-16T15:04:04,729 copying build/lib/seal5/backends/riscv_register_info/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_register_info 2025-12-16T15:04:04,732 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_field_types 2025-12-16T15:04:04,733 copying build/lib/seal5/backends/riscv_field_types/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_field_types 2025-12-16T15:04:04,735 copying build/lib/seal5/backends/riscv_field_types/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_field_types 2025-12-16T15:04:04,738 copying build/lib/seal5/backends/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends 2025-12-16T15:04:04,740 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_isa_info 2025-12-16T15:04:04,741 copying build/lib/seal5/backends/riscv_isa_info/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_isa_info 2025-12-16T15:04:04,743 copying build/lib/seal5/backends/riscv_isa_info/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_isa_info 2025-12-16T15:04:04,746 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_intrinsics 2025-12-16T15:04:04,747 copying build/lib/seal5/backends/riscv_intrinsics/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_intrinsics 2025-12-16T15:04:04,748 copying build/lib/seal5/backends/riscv_intrinsics/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_intrinsics 2025-12-16T15:04:04,751 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_gisel_legalizer 2025-12-16T15:04:04,752 copying build/lib/seal5/backends/riscv_gisel_legalizer/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_gisel_legalizer 2025-12-16T15:04:04,754 copying build/lib/seal5/backends/riscv_gisel_legalizer/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_gisel_legalizer 2025-12-16T15:04:04,757 creating build/bdist.linux-armv7l/wheel/seal5/backends/viewer_seal5 2025-12-16T15:04:04,758 copying build/lib/seal5/backends/viewer_seal5/viewer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/viewer_seal5 2025-12-16T15:04:04,760 copying build/lib/seal5/backends/viewer_seal5/utils.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/viewer_seal5 2025-12-16T15:04:04,762 copying build/lib/seal5/backends/viewer_seal5/treegen.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/viewer_seal5 2025-12-16T15:04:04,764 copying build/lib/seal5/backends/viewer_seal5/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/viewer_seal5 2025-12-16T15:04:04,767 creating build/bdist.linux-armv7l/wheel/seal5/transform 2025-12-16T15:04:04,768 creating build/bdist.linux-armv7l/wheel/seal5/transform/collect_immediate_operands 2025-12-16T15:04:04,769 copying build/lib/seal5/transform/collect_immediate_operands/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_immediate_operands 2025-12-16T15:04:04,771 copying build/lib/seal5/transform/collect_immediate_operands/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_immediate_operands 2025-12-16T15:04:04,773 copying build/lib/seal5/transform/collect_immediate_operands/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_immediate_operands 2025-12-16T15:04:04,776 creating build/bdist.linux-armv7l/wheel/seal5/transform/collect_operand_types 2025-12-16T15:04:04,777 copying build/lib/seal5/transform/collect_operand_types/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_operand_types 2025-12-16T15:04:04,779 copying build/lib/seal5/transform/collect_operand_types/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_operand_types 2025-12-16T15:04:04,781 copying build/lib/seal5/transform/collect_operand_types/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_operand_types 2025-12-16T15:04:04,784 creating build/bdist.linux-armv7l/wheel/seal5/transform/collect_raises 2025-12-16T15:04:04,785 copying build/lib/seal5/transform/collect_raises/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_raises 2025-12-16T15:04:04,787 copying build/lib/seal5/transform/collect_raises/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_raises 2025-12-16T15:04:04,789 copying build/lib/seal5/transform/collect_raises/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_raises 2025-12-16T15:04:04,792 creating build/bdist.linux-armv7l/wheel/seal5/transform/collect_register_operands 2025-12-16T15:04:04,793 copying build/lib/seal5/transform/collect_register_operands/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_register_operands 2025-12-16T15:04:04,795 copying build/lib/seal5/transform/collect_register_operands/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_register_operands 2025-12-16T15:04:04,797 copying build/lib/seal5/transform/collect_register_operands/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_register_operands 2025-12-16T15:04:04,800 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_inouts 2025-12-16T15:04:04,801 copying build/lib/seal5/transform/detect_inouts/utils.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_inouts 2025-12-16T15:04:04,803 copying build/lib/seal5/transform/detect_inouts/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_inouts 2025-12-16T15:04:04,805 copying build/lib/seal5/transform/detect_inouts/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_inouts 2025-12-16T15:04:04,807 copying build/lib/seal5/transform/detect_inouts/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_inouts 2025-12-16T15:04:04,810 creating build/bdist.linux-armv7l/wheel/seal5/transform/eliminate_mod_rfs 2025-12-16T15:04:04,811 copying build/lib/seal5/transform/eliminate_mod_rfs/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_mod_rfs 2025-12-16T15:04:04,814 copying build/lib/seal5/transform/eliminate_mod_rfs/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_mod_rfs 2025-12-16T15:04:04,816 copying build/lib/seal5/transform/eliminate_mod_rfs/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_mod_rfs 2025-12-16T15:04:04,819 creating build/bdist.linux-armv7l/wheel/seal5/transform/filter_model 2025-12-16T15:04:04,820 copying build/lib/seal5/transform/filter_model/filter.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/filter_model 2025-12-16T15:04:04,823 copying build/lib/seal5/transform/filter_model/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/filter_model 2025-12-16T15:04:04,826 creating build/bdist.linux-armv7l/wheel/seal5/transform/infer_types 2025-12-16T15:04:04,828 copying build/lib/seal5/transform/infer_types/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/infer_types 2025-12-16T15:04:04,830 copying build/lib/seal5/transform/infer_types/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/infer_types 2025-12-16T15:04:04,833 copying build/lib/seal5/transform/infer_types/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/infer_types 2025-12-16T15:04:04,836 creating build/bdist.linux-armv7l/wheel/seal5/transform/drop_unused 2025-12-16T15:04:04,837 copying build/lib/seal5/transform/drop_unused/optimizer.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/drop_unused 2025-12-16T15:04:04,840 copying build/lib/seal5/transform/drop_unused/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/drop_unused 2025-12-16T15:04:04,842 copying build/lib/seal5/transform/drop_unused/track_uses.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/drop_unused 2025-12-16T15:04:04,845 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_imm_leafs 2025-12-16T15:04:04,846 copying build/lib/seal5/transform/detect_imm_leafs/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_imm_leafs 2025-12-16T15:04:04,849 copying build/lib/seal5/transform/detect_imm_leafs/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_imm_leafs 2025-12-16T15:04:04,852 copying build/lib/seal5/transform/detect_imm_leafs/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_imm_leafs 2025-12-16T15:04:04,855 creating build/bdist.linux-armv7l/wheel/seal5/transform/annotate_opcodes 2025-12-16T15:04:04,856 copying build/lib/seal5/transform/annotate_opcodes/annotate.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/annotate_opcodes 2025-12-16T15:04:04,859 copying build/lib/seal5/transform/annotate_opcodes/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/annotate_opcodes 2025-12-16T15:04:04,862 creating build/bdist.linux-armv7l/wheel/seal5/transform/explicit_truncations 2025-12-16T15:04:04,863 copying build/lib/seal5/transform/explicit_truncations/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/explicit_truncations 2025-12-16T15:04:04,867 copying build/lib/seal5/transform/explicit_truncations/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/explicit_truncations 2025-12-16T15:04:04,869 copying build/lib/seal5/transform/explicit_truncations/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/explicit_truncations 2025-12-16T15:04:04,872 copying build/lib/seal5/transform/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform 2025-12-16T15:04:04,875 creating build/bdist.linux-armv7l/wheel/seal5/transform/eliminate_rd_cmp_zero 2025-12-16T15:04:04,876 copying build/lib/seal5/transform/eliminate_rd_cmp_zero/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_rd_cmp_zero 2025-12-16T15:04:04,879 copying build/lib/seal5/transform/eliminate_rd_cmp_zero/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_rd_cmp_zero 2025-12-16T15:04:04,881 copying build/lib/seal5/transform/eliminate_rd_cmp_zero/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_rd_cmp_zero 2025-12-16T15:04:04,884 creating build/bdist.linux-armv7l/wheel/seal5/transform/simplify_trivial_slices 2025-12-16T15:04:04,885 copying build/lib/seal5/transform/simplify_trivial_slices/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/simplify_trivial_slices 2025-12-16T15:04:04,888 copying build/lib/seal5/transform/simplify_trivial_slices/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/simplify_trivial_slices 2025-12-16T15:04:04,890 copying build/lib/seal5/transform/simplify_trivial_slices/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/simplify_trivial_slices 2025-12-16T15:04:04,893 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_registers 2025-12-16T15:04:04,895 copying build/lib/seal5/transform/detect_registers/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_registers 2025-12-16T15:04:04,897 copying build/lib/seal5/transform/detect_registers/detect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_registers 2025-12-16T15:04:04,900 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_calls 2025-12-16T15:04:04,902 copying build/lib/seal5/transform/detect_calls/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_calls 2025-12-16T15:04:04,904 copying build/lib/seal5/transform/detect_calls/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_calls 2025-12-16T15:04:04,907 copying build/lib/seal5/transform/detect_calls/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_calls 2025-12-16T15:04:04,910 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_side_effects 2025-12-16T15:04:04,911 copying build/lib/seal5/transform/detect_side_effects/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_side_effects 2025-12-16T15:04:04,913 copying build/lib/seal5/transform/detect_side_effects/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_side_effects 2025-12-16T15:04:04,915 copying build/lib/seal5/transform/detect_side_effects/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_side_effects 2025-12-16T15:04:04,918 creating build/bdist.linux-armv7l/wheel/seal5/transform/process_settings 2025-12-16T15:04:04,919 copying build/lib/seal5/transform/process_settings/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/process_settings 2025-12-16T15:04:04,921 copying build/lib/seal5/transform/process_settings/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/process_settings 2025-12-16T15:04:04,923 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_loops 2025-12-16T15:04:04,924 copying build/lib/seal5/transform/detect_loops/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_loops 2025-12-16T15:04:04,927 copying build/lib/seal5/transform/detect_loops/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_loops 2025-12-16T15:04:04,929 copying build/lib/seal5/transform/detect_loops/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_loops 2025-12-16T15:04:04,931 creating build/bdist.linux-armv7l/wheel/seal5/transform/check_pattern_support 2025-12-16T15:04:04,932 copying build/lib/seal5/transform/check_pattern_support/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/check_pattern_support 2025-12-16T15:04:04,934 copying build/lib/seal5/transform/check_pattern_support/check.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/check_pattern_support 2025-12-16T15:04:04,936 copying build/lib/seal5/transform/converter.py -> build/bdist.linux-armv7l/wheel/./seal5/transform 2025-12-16T15:04:04,939 creating build/bdist.linux-armv7l/wheel/seal5/transform/optimize_instructions 2025-12-16T15:04:04,940 copying build/lib/seal5/transform/optimize_instructions/optimizer.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/optimize_instructions 2025-12-16T15:04:04,942 copying build/lib/seal5/transform/optimize_instructions/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/optimize_instructions 2025-12-16T15:04:04,945 creating build/bdist.linux-armv7l/wheel/seal5/transform/inline_functions 2025-12-16T15:04:04,946 copying build/lib/seal5/transform/inline_functions/optimizer.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/inline_functions 2025-12-16T15:04:04,947 copying build/lib/seal5/transform/inline_functions/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/inline_functions 2025-12-16T15:04:04,950 copying build/lib/seal5/transform/inline_functions/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/inline_functions 2025-12-16T15:04:04,951 running install_egg_info 2025-12-16T15:04:04,959 Copying seal5.egg-info to build/bdist.linux-armv7l/wheel/./seal5-0.3.3-py3.11.egg-info 2025-12-16T15:04:04,972 running install_scripts 2025-12-16T15:04:04,985 creating build/bdist.linux-armv7l/wheel/seal5-0.3.3.dist-info/WHEEL 2025-12-16T15:04:04,988 creating '/tmp/pip-wheel-wgbks3kz/.tmp-uc92unpw/seal5-0.3.3-py3-none-any.whl' and adding 'build/bdist.linux-armv7l/wheel' to it 2025-12-16T15:04:04,991 adding 'seal5/__init__.py' 2025-12-16T15:04:04,992 adding 'seal5/build_cache.py' 2025-12-16T15:04:04,994 adding 'seal5/dependencies.py' 2025-12-16T15:04:04,999 adding 'seal5/flow.py' 2025-12-16T15:04:05,001 adding 'seal5/index.py' 2025-12-16T15:04:05,003 adding 'seal5/logging.py' 2025-12-16T15:04:05,004 adding 'seal5/metrics.py' 2025-12-16T15:04:05,007 adding 'seal5/model.py' 2025-12-16T15:04:05,009 adding 'seal5/model_utils.py' 2025-12-16T15:04:05,013 adding 'seal5/pass_list.py' 2025-12-16T15:04:05,016 adding 'seal5/passes.py' 2025-12-16T15:04:05,017 adding 'seal5/riscv_utils.py' 2025-12-16T15:04:05,020 adding 'seal5/settings.py' 2025-12-16T15:04:05,022 adding 'seal5/testgen_utils.py' 2025-12-16T15:04:05,023 adding 'seal5/types.py' 2025-12-16T15:04:05,025 adding 'seal5/utils.py' 2025-12-16T15:04:05,026 adding 'seal5/version.py' 2025-12-16T15:04:05,027 adding 'seal5/wrapper.py' 2025-12-16T15:04:05,029 adding 'seal5/backends/__init__.py' 2025-12-16T15:04:05,031 adding 'seal5/backends/coredsl2/__init__.py' 2025-12-16T15:04:05,033 adding 'seal5/backends/coredsl2/visitor.py' 2025-12-16T15:04:05,035 adding 'seal5/backends/coredsl2/writer.py' 2025-12-16T15:04:05,037 adding 'seal5/backends/llvmir/__init__.py' 2025-12-16T15:04:05,038 adding 'seal5/backends/llvmir/writer.py' 2025-12-16T15:04:05,040 adding 'seal5/backends/patterngen/__init__.py' 2025-12-16T15:04:05,042 adding 'seal5/backends/patterngen/writer.py' 2025-12-16T15:04:05,044 adding 'seal5/backends/report/__init__.py' 2025-12-16T15:04:05,046 adding 'seal5/backends/report/diff/__init__.py' 2025-12-16T15:04:05,047 adding 'seal5/backends/report/diff/writer.py' 2025-12-16T15:04:05,049 adding 'seal5/backends/report/pattern_gen/__init__.py' 2025-12-16T15:04:05,050 adding 'seal5/backends/report/pattern_gen/writer.py' 2025-12-16T15:04:05,052 adding 'seal5/backends/report/properties/__init__.py' 2025-12-16T15:04:05,054 adding 'seal5/backends/report/properties/writer.py' 2025-12-16T15:04:05,056 adding 'seal5/backends/report/status/__init__.py' 2025-12-16T15:04:05,058 adding 'seal5/backends/report/status/writer.py' 2025-12-16T15:04:05,059 adding 'seal5/backends/report/test_results/__init__.py' 2025-12-16T15:04:05,062 adding 'seal5/backends/report/test_results/writer.py' 2025-12-16T15:04:05,064 adding 'seal5/backends/report/times/__init__.py' 2025-12-16T15:04:05,065 adding 'seal5/backends/report/times/writer.py' 2025-12-16T15:04:05,067 adding 'seal5/backends/riscv_features/__init__.py' 2025-12-16T15:04:05,069 adding 'seal5/backends/riscv_features/writer.py' 2025-12-16T15:04:05,071 adding 'seal5/backends/riscv_features/templates/__init__.py' 2025-12-16T15:04:05,072 adding 'seal5/backends/riscv_features/templates/riscv_features.mako' 2025-12-16T15:04:05,073 adding 'seal5/backends/riscv_features/templates/riscv_features_experimental_new.mako' 2025-12-16T15:04:05,074 adding 'seal5/backends/riscv_features/templates/riscv_features_experimental_new_slim.mako' 2025-12-16T15:04:05,075 adding 'seal5/backends/riscv_features/templates/riscv_features_new.mako' 2025-12-16T15:04:05,076 adding 'seal5/backends/riscv_features/templates/riscv_features_new_slim.mako' 2025-12-16T15:04:05,077 adding 'seal5/backends/riscv_features/templates/test_riscv_attributes.mako' 2025-12-16T15:04:05,079 adding 'seal5/backends/riscv_field_types/__init__.py' 2025-12-16T15:04:05,081 adding 'seal5/backends/riscv_field_types/writer.py' 2025-12-16T15:04:05,083 adding 'seal5/backends/riscv_gisel_legalizer/__init__.py' 2025-12-16T15:04:05,084 adding 'seal5/backends/riscv_gisel_legalizer/writer.py' 2025-12-16T15:04:05,086 adding 'seal5/backends/riscv_instr_info/__init__.py' 2025-12-16T15:04:05,088 adding 'seal5/backends/riscv_instr_info/writer.py' 2025-12-16T15:04:05,090 adding 'seal5/backends/riscv_instr_info/templates/__init__.py' 2025-12-16T15:04:05,091 adding 'seal5/backends/riscv_instr_info/templates/instr_tablegen.mako' 2025-12-16T15:04:05,093 adding 'seal5/backends/riscv_intrinsics/__init__.py' 2025-12-16T15:04:05,095 adding 'seal5/backends/riscv_intrinsics/writer.py' 2025-12-16T15:04:05,097 adding 'seal5/backends/riscv_isa_info/__init__.py' 2025-12-16T15:04:05,098 adding 'seal5/backends/riscv_isa_info/writer.py' 2025-12-16T15:04:05,100 adding 'seal5/backends/riscv_register_info/__init__.py' 2025-12-16T15:04:05,102 adding 'seal5/backends/riscv_register_info/writer.py' 2025-12-16T15:04:05,104 adding 'seal5/backends/viewer_seal5/__init__.py' 2025-12-16T15:04:05,105 adding 'seal5/backends/viewer_seal5/treegen.py' 2025-12-16T15:04:05,107 adding 'seal5/backends/viewer_seal5/utils.py' 2025-12-16T15:04:05,109 adding 'seal5/backends/viewer_seal5/viewer.py' 2025-12-16T15:04:05,110 adding 'seal5/backends/yaml/__init__.py' 2025-12-16T15:04:05,112 adding 'seal5/backends/yaml/writer.py' 2025-12-16T15:04:05,114 adding 'seal5/cli/__init__.py' 2025-12-16T15:04:05,115 adding 'seal5/cli/build.py' 2025-12-16T15:04:05,116 adding 'seal5/cli/clean.py' 2025-12-16T15:04:05,118 adding 'seal5/cli/common.py' 2025-12-16T15:04:05,119 adding 'seal5/cli/deploy.py' 2025-12-16T15:04:05,120 adding 'seal5/cli/export.py' 2025-12-16T15:04:05,122 adding 'seal5/cli/generate.py' 2025-12-16T15:04:05,123 adding 'seal5/cli/init.py' 2025-12-16T15:04:05,124 adding 'seal5/cli/install.py' 2025-12-16T15:04:05,126 adding 'seal5/cli/load.py' 2025-12-16T15:04:05,127 adding 'seal5/cli/main.py' 2025-12-16T15:04:05,128 adding 'seal5/cli/patch.py' 2025-12-16T15:04:05,130 adding 'seal5/cli/reset.py' 2025-12-16T15:04:05,131 adding 'seal5/cli/setup.py' 2025-12-16T15:04:05,132 adding 'seal5/cli/test.py' 2025-12-16T15:04:05,134 adding 'seal5/cli/transform.py' 2025-12-16T15:04:05,135 adding 'seal5/cli/wrapper.py' 2025-12-16T15:04:05,137 adding 'seal5/frontends/coredsl2_seal5/.gitignore' 2025-12-16T15:04:05,139 adding 'seal5/frontends/coredsl2_seal5/CoreDSL2.g4' 2025-12-16T15:04:05,140 adding 'seal5/frontends/coredsl2_seal5/README.md' 2025-12-16T15:04:05,142 adding 'seal5/frontends/coredsl2_seal5/__init__.py' 2025-12-16T15:04:05,143 adding 'seal5/frontends/coredsl2_seal5/antlr.sh' 2025-12-16T15:04:05,145 adding 'seal5/frontends/coredsl2_seal5/architecture_model_builder.py' 2025-12-16T15:04:05,148 adding 'seal5/frontends/coredsl2_seal5/behavior_model_builder.py' 2025-12-16T15:04:05,149 adding 'seal5/frontends/coredsl2_seal5/expr_interpreter.py' 2025-12-16T15:04:05,150 adding 'seal5/frontends/coredsl2_seal5/importer.py' 2025-12-16T15:04:05,152 adding 'seal5/frontends/coredsl2_seal5/load_order.py' 2025-12-16T15:04:05,154 adding 'seal5/frontends/coredsl2_seal5/parser.py' 2025-12-16T15:04:05,155 adding 'seal5/frontends/coredsl2_seal5/utils.py' 2025-12-16T15:04:05,157 adding 'seal5/frontends/coredsl2_seal5/parser_gen/.gitignore' 2025-12-16T15:04:05,162 adding 'seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Lexer.py' 2025-12-16T15:04:05,164 adding 'seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Listener.py' 2025-12-16T15:04:05,180 adding 'seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Parser.py' 2025-12-16T15:04:05,183 adding 'seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Visitor.py' 2025-12-16T15:04:05,185 adding 'seal5/frontends/coredsl2_seal5/parser_gen/__init__.py' 2025-12-16T15:04:05,186 adding 'seal5/resources/__init__.py' 2025-12-16T15:04:05,188 adding 'seal5/resources/lit.cfg.py' 2025-12-16T15:04:05,189 adding 'seal5/resources/resources.py' 2025-12-16T15:04:05,191 adding 'seal5/resources/patches/llvm/github_ci.patch' 2025-12-16T15:04:05,192 adding 'seal5/resources/patches/llvm/gitignore.patch' 2025-12-16T15:04:05,193 adding 'seal5/resources/patches/llvm/gitlab_ci.patch' 2025-12-16T15:04:05,195 adding 'seal5/resources/patches/llvm/insert_markers_llvm17.patch' 2025-12-16T15:04:05,197 adding 'seal5/resources/patches/llvm/insert_markers_llvm18.patch' 2025-12-16T15:04:05,198 adding 'seal5/resources/patches/llvm/insert_markers_llvm19.patch' 2025-12-16T15:04:05,200 adding 'seal5/resources/patches/llvm/insert_markers_llvm20.patch' 2025-12-16T15:04:05,201 adding 'seal5/resources/patches/llvm/insert_markers_llvm21.patch' 2025-12-16T15:04:05,203 adding 'seal5/resources/patches/llvm/legalizer_fix_1.patch' 2025-12-16T15:04:05,204 adding 'seal5/resources/patches/llvm/legalizer_fix_2.patch' 2025-12-16T15:04:05,205 adding 'seal5/resources/patches/llvm/legalizer_split.patch' 2025-12-16T15:04:05,206 adding 'seal5/resources/patches/llvm/regclass_gpr32v.patch' 2025-12-16T15:04:05,208 adding 'seal5/resources/patches/llvm/simd_gpr32v.patch' 2025-12-16T15:04:05,209 adding 'seal5/tools/__init__.py' 2025-12-16T15:04:05,211 adding 'seal5/tools/cdsl2llvm.py' 2025-12-16T15:04:05,213 adding 'seal5/tools/cmake.py' 2025-12-16T15:04:05,214 adding 'seal5/tools/git.py' 2025-12-16T15:04:05,216 adding 'seal5/tools/inject_patches.py' 2025-12-16T15:04:05,218 adding 'seal5/tools/llvm.py' 2025-12-16T15:04:05,219 adding 'seal5/tools/m2isar.py' 2025-12-16T15:04:05,221 adding 'seal5/transform/__init__.py' 2025-12-16T15:04:05,222 adding 'seal5/transform/converter.py' 2025-12-16T15:04:05,224 adding 'seal5/transform/annotate_opcodes/__init__.py' 2025-12-16T15:04:05,226 adding 'seal5/transform/annotate_opcodes/annotate.py' 2025-12-16T15:04:05,228 adding 'seal5/transform/check_pattern_support/__init__.py' 2025-12-16T15:04:05,229 adding 'seal5/transform/check_pattern_support/check.py' 2025-12-16T15:04:05,231 adding 'seal5/transform/collect_immediate_operands/__init__.py' 2025-12-16T15:04:05,232 adding 'seal5/transform/collect_immediate_operands/collect.py' 2025-12-16T15:04:05,234 adding 'seal5/transform/collect_immediate_operands/visitor.py' 2025-12-16T15:04:05,236 adding 'seal5/transform/collect_operand_types/__init__.py' 2025-12-16T15:04:05,237 adding 'seal5/transform/collect_operand_types/collect.py' 2025-12-16T15:04:05,239 adding 'seal5/transform/collect_operand_types/visitor.py' 2025-12-16T15:04:05,241 adding 'seal5/transform/collect_raises/__init__.py' 2025-12-16T15:04:05,242 adding 'seal5/transform/collect_raises/collect.py' 2025-12-16T15:04:05,244 adding 'seal5/transform/collect_raises/visitor.py' 2025-12-16T15:04:05,245 adding 'seal5/transform/collect_register_operands/__init__.py' 2025-12-16T15:04:05,247 adding 'seal5/transform/collect_register_operands/collect.py' 2025-12-16T15:04:05,248 adding 'seal5/transform/collect_register_operands/visitor.py' 2025-12-16T15:04:05,250 adding 'seal5/transform/detect_calls/__init__.py' 2025-12-16T15:04:05,252 adding 'seal5/transform/detect_calls/collect.py' 2025-12-16T15:04:05,253 adding 'seal5/transform/detect_calls/visitor.py' 2025-12-16T15:04:05,255 adding 'seal5/transform/detect_imm_leafs/__init__.py' 2025-12-16T15:04:05,256 adding 'seal5/transform/detect_imm_leafs/collect.py' 2025-12-16T15:04:05,257 adding 'seal5/transform/detect_imm_leafs/visitor.py' 2025-12-16T15:04:05,259 adding 'seal5/transform/detect_inouts/__init__.py' 2025-12-16T15:04:05,260 adding 'seal5/transform/detect_inouts/collect.py' 2025-12-16T15:04:05,262 adding 'seal5/transform/detect_inouts/utils.py' 2025-12-16T15:04:05,263 adding 'seal5/transform/detect_inouts/visitor.py' 2025-12-16T15:04:05,265 adding 'seal5/transform/detect_loops/__init__.py' 2025-12-16T15:04:05,266 adding 'seal5/transform/detect_loops/collect.py' 2025-12-16T15:04:05,267 adding 'seal5/transform/detect_loops/visitor.py' 2025-12-16T15:04:05,269 adding 'seal5/transform/detect_registers/__init__.py' 2025-12-16T15:04:05,270 adding 'seal5/transform/detect_registers/detect.py' 2025-12-16T15:04:05,272 adding 'seal5/transform/detect_side_effects/__init__.py' 2025-12-16T15:04:05,274 adding 'seal5/transform/detect_side_effects/collect.py' 2025-12-16T15:04:05,275 adding 'seal5/transform/detect_side_effects/visitor.py' 2025-12-16T15:04:05,277 adding 'seal5/transform/drop_unused/__init__.py' 2025-12-16T15:04:05,278 adding 'seal5/transform/drop_unused/optimizer.py' 2025-12-16T15:04:05,279 adding 'seal5/transform/drop_unused/track_uses.py' 2025-12-16T15:04:05,281 adding 'seal5/transform/eliminate_mod_rfs/__init__.py' 2025-12-16T15:04:05,282 adding 'seal5/transform/eliminate_mod_rfs/transform.py' 2025-12-16T15:04:05,284 adding 'seal5/transform/eliminate_mod_rfs/visitor.py' 2025-12-16T15:04:05,285 adding 'seal5/transform/eliminate_rd_cmp_zero/__init__.py' 2025-12-16T15:04:05,287 adding 'seal5/transform/eliminate_rd_cmp_zero/transform.py' 2025-12-16T15:04:05,288 adding 'seal5/transform/eliminate_rd_cmp_zero/visitor.py' 2025-12-16T15:04:05,290 adding 'seal5/transform/explicit_truncations/__init__.py' 2025-12-16T15:04:05,291 adding 'seal5/transform/explicit_truncations/transform.py' 2025-12-16T15:04:05,293 adding 'seal5/transform/explicit_truncations/visitor.py' 2025-12-16T15:04:05,294 adding 'seal5/transform/filter_model/__init__.py' 2025-12-16T15:04:05,296 adding 'seal5/transform/filter_model/filter.py' 2025-12-16T15:04:05,298 adding 'seal5/transform/infer_types/__init__.py' 2025-12-16T15:04:05,299 adding 'seal5/transform/infer_types/transform.py' 2025-12-16T15:04:05,301 adding 'seal5/transform/infer_types/visitor.py' 2025-12-16T15:04:05,303 adding 'seal5/transform/inline_functions/__init__.py' 2025-12-16T15:04:05,304 adding 'seal5/transform/inline_functions/optimizer.py' 2025-12-16T15:04:05,306 adding 'seal5/transform/inline_functions/visitor.py' 2025-12-16T15:04:05,308 adding 'seal5/transform/optimize_instructions/__init__.py' 2025-12-16T15:04:05,309 adding 'seal5/transform/optimize_instructions/optimizer.py' 2025-12-16T15:04:05,311 adding 'seal5/transform/process_settings/__init__.py' 2025-12-16T15:04:05,312 adding 'seal5/transform/process_settings/transform.py' 2025-12-16T15:04:05,314 adding 'seal5/transform/simplify_trivial_slices/__init__.py' 2025-12-16T15:04:05,316 adding 'seal5/transform/simplify_trivial_slices/transform.py' 2025-12-16T15:04:05,317 adding 'seal5/transform/simplify_trivial_slices/visitor.py' 2025-12-16T15:04:05,321 adding 'seal5-0.3.3.dist-info/licenses/LICENSE' 2025-12-16T15:04:05,323 adding 'seal5-0.3.3.dist-info/METADATA' 2025-12-16T15:04:05,324 adding 'seal5-0.3.3.dist-info/WHEEL' 2025-12-16T15:04:05,325 adding 'seal5-0.3.3.dist-info/entry_points.txt' 2025-12-16T15:04:05,326 adding 'seal5-0.3.3.dist-info/top_level.txt' 2025-12-16T15:04:05,329 adding 'seal5-0.3.3.dist-info/RECORD' 2025-12-16T15:04:05,336 removing build/bdist.linux-armv7l/wheel 2025-12-16T15:04:05,500 Building wheel for seal5 (pyproject.toml): finished with status 'done' 2025-12-16T15:04:05,513 Created wheel for seal5: filename=seal5-0.3.3-py3-none-any.whl size=321192 sha256=98d4450814a242d8ebc874e3521b64effb19563fe460c4894cc4a906655a4986 2025-12-16T15:04:05,514 Stored in directory: /tmp/pip-ephem-wheel-cache-ay09v5t0/wheels/9b/79/16/0d559f4cf973dd6bd6bcf832604b1a51df08bf74d272cc06a9 2025-12-16T15:04:05,531 Successfully built seal5 2025-12-16T15:04:05,546 Removed build tracker: '/tmp/pip-build-tracker-yu7v86hm'