python3.14-vicinity-0.4.4
checks.x86_64-linux.pkgs-semble
· build #8258
· raw
1structuredAttrs is enabled2Sourcing python-remove-tests-dir-hook3Sourcing python-catch-conflicts-hook.sh4Sourcing python-remove-bin-bytecode-hook.sh5Sourcing pypa-build-hook6Using pypaBuildPhase7Sourcing python-runtime-deps-check-hook8Using pythonRuntimeDepsCheckHook9Sourcing pypa-install-hook10Using pypaInstallPhase11Sourcing python-imports-check-hook.sh12Using pythonImportsCheckPhase13Sourcing python-metadata-check-hook.sh14Using pythonMetadataCheckPhase15Sourcing python-namespaces-hook16Sourcing python-catch-conflicts-hook.sh17Using checkPhaseThreadLimitHook
unpackPhase
18unpacking source archive /nix/store/vcrp5i7fav7h0x98gqspihdrkwqb6710-vicinity-0.4.4.tar.gz19source root is vicinity-0.4.420setting SOURCE_DATE_EPOCH to timestamp 1776179318 of file "vicinity-0.4.4/setup.cfg"configurePhase
21no configure script, doing nothingbuildPhase
22Executing pypaBuildPhase23Including all tracked files automatically24Creating a wheel...25pypa build flags: --no-isolation --outdir dist/ --wheel26* Getting build dependencies for wheel...27/nix/store/gbx4g3vl293h21nmqbviqmpwb2r0q9dw-python3.14-setuptools-scm-10.2.1/lib/python3.14/site-packages/setuptools_scm/_integration/deprecation.py:9: UserWarning: pyproject.toml: at [tool.setuptools.dynamic]28version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set29When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.30Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.31 warnings.warn(32/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated33!!3435 ********************************************************************************36 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).3738 By 2027-Feb-18, you need to update your project and remove deprecated calls39 or your builds will no longer be supported.4041 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.42 ********************************************************************************4344!!45 corresp(dist, value, root_dir)46/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:55: SetuptoolsDeprecationWarning: 'tool.setuptools.license-files' is deprecated in favor of 'project.license-files' (available on setuptools>=77.0.0).47!!4849 ********************************************************************************5051 By 2027-Feb-18, you need to update your project and remove deprecated calls52 or your builds will no longer be supported.5354 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-files for details.55 ********************************************************************************5657!!58 _apply_tool_table(dist, config, filename)59/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated.60!!6162 ********************************************************************************63 Please consider removing the following classifiers in favor of a SPDX license expression:6465 License :: OSI Approved :: MIT License6667 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.68 ********************************************************************************6970!!71 dist._finalize_license_expression()72/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.73!!7475 ********************************************************************************76 Please consider removing the following classifiers in favor of a SPDX license expression:7778 License :: OSI Approved :: MIT License7980 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.81 ********************************************************************************8283!!84 self._finalize_license_expression()85running egg_info86writing vicinity.egg-info/PKG-INFO87writing dependency_links to vicinity.egg-info/dependency_links.txt88writing requirements to vicinity.egg-info/requires.txt89writing top-level names to vicinity.egg-info/top_level.txt90reading manifest file 'vicinity.egg-info/SOURCES.txt'91reading manifest template 'MANIFEST.in'92writing manifest file 'vicinity.egg-info/SOURCES.txt'93* Building wheel...94/nix/store/gbx4g3vl293h21nmqbviqmpwb2r0q9dw-python3.14-setuptools-scm-10.2.1/lib/python3.14/site-packages/setuptools_scm/_integration/deprecation.py:9: UserWarning: pyproject.toml: at [tool.setuptools.dynamic]95version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set96When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.97Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.98 warnings.warn(99/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated100!!101102 ********************************************************************************103 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).104105 By 2027-Feb-18, you need to update your project and remove deprecated calls106 or your builds will no longer be supported.107108 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.109 ********************************************************************************110111!!112 corresp(dist, value, root_dir)113/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:55: SetuptoolsDeprecationWarning: 'tool.setuptools.license-files' is deprecated in favor of 'project.license-files' (available on setuptools>=77.0.0).114!!115116 ********************************************************************************117118 By 2027-Feb-18, you need to update your project and remove deprecated calls119 or your builds will no longer be supported.120121 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-files for details.122 ********************************************************************************123124!!125 _apply_tool_table(dist, config, filename)126/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated.127!!128129 ********************************************************************************130 Please consider removing the following classifiers in favor of a SPDX license expression:131132 License :: OSI Approved :: MIT License133134 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.135 ********************************************************************************136137!!138 dist._finalize_license_expression()139/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.140!!141142 ********************************************************************************143 Please consider removing the following classifiers in favor of a SPDX license expression:144145 License :: OSI Approved :: MIT License146147 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.148 ********************************************************************************149150!!151 self._finalize_license_expression()152running bdist_wheel153running build154running build_py155creating build/lib/vicinity156copying vicinity/__init__.py -> build/lib/vicinity157copying vicinity/vicinity.py -> build/lib/vicinity158copying vicinity/datatypes.py -> build/lib/vicinity159copying vicinity/utils.py -> build/lib/vicinity160copying vicinity/version.py -> build/lib/vicinity161running egg_info162writing vicinity.egg-info/PKG-INFO163writing dependency_links to vicinity.egg-info/dependency_links.txt164writing requirements to vicinity.egg-info/requires.txt165writing top-level names to vicinity.egg-info/top_level.txt166reading manifest file 'vicinity.egg-info/SOURCES.txt'167reading manifest template 'MANIFEST.in'168writing manifest file 'vicinity.egg-info/SOURCES.txt'169/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'vicinity.__pycache__' is absent from the `packages` configuration.170!!171172 ********************************************************************************173 ############################174 # Package would be ignored #175 ############################176 Python recognizes 'vicinity.__pycache__' as an importable package[^1],177 but it is absent from setuptools' `packages` configuration.178179 This leads to an ambiguous overall configuration. If you want to distribute this180 package, please make sure that 'vicinity.__pycache__' is explicitly added181 to the `packages` configuration field.182183 Alternatively, you can also rely on setuptools' discovery methods184 (for example by using `find_namespace_packages(...)`/`find_namespace:`185 instead of `find_packages(...)`/`find:`).186187 You can read more about "package discovery" on setuptools documentation page:188189 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html190191 If you don't want 'vicinity.__pycache__' to be distributed and are192 already explicitly excluding 'vicinity.__pycache__' via193 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,194 you can try to use `exclude_package_data`, or `include-package-data=False` in195 combination with a more fine grained `package-data` configuration.196197 You can read more about "package data files" on setuptools documentation page:198199 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html200201202 [^1]: For Python, any directory (with suitable naming) can be imported,203 even if it does not contain any `.py` files.204 On the other hand, currently there is no concept of package data205 directory, all directories are treated like packages.206 ********************************************************************************207208!!209 check.warn(importable)210/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'vicinity.backends' is absent from the `packages` configuration.211!!212213 ********************************************************************************214 ############################215 # Package would be ignored #216 ############################217 Python recognizes 'vicinity.backends' as an importable package[^1],218 but it is absent from setuptools' `packages` configuration.219220 This leads to an ambiguous overall configuration. If you want to distribute this221 package, please make sure that 'vicinity.backends' is explicitly added222 to the `packages` configuration field.223224 Alternatively, you can also rely on setuptools' discovery methods225 (for example by using `find_namespace_packages(...)`/`find_namespace:`226 instead of `find_packages(...)`/`find:`).227228 You can read more about "package discovery" on setuptools documentation page:229230 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html231232 If you don't want 'vicinity.backends' to be distributed and are233 already explicitly excluding 'vicinity.backends' via234 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,235 you can try to use `exclude_package_data`, or `include-package-data=False` in236 combination with a more fine grained `package-data` configuration.237238 You can read more about "package data files" on setuptools documentation page:239240 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html241242243 [^1]: For Python, any directory (with suitable naming) can be imported,244 even if it does not contain any `.py` files.245 On the other hand, currently there is no concept of package data246 directory, all directories are treated like packages.247 ********************************************************************************248249!!250 check.warn(importable)251/nix/store/d13f804szzqg28s2i8rbqwlcz2wg63w9-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'vicinity.integrations' is absent from the `packages` configuration.252!!253254 ********************************************************************************255 ############################256 # Package would be ignored #257 ############################258 Python recognizes 'vicinity.integrations' as an importable package[^1],259 but it is absent from setuptools' `packages` configuration.260261 This leads to an ambiguous overall configuration. If you want to distribute this262 package, please make sure that 'vicinity.integrations' is explicitly added263 to the `packages` configuration field.264265 Alternatively, you can also rely on setuptools' discovery methods266 (for example by using `find_namespace_packages(...)`/`find_namespace:`267 instead of `find_packages(...)`/`find:`).268269 You can read more about "package discovery" on setuptools documentation page:270271 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html272273 If you don't want 'vicinity.integrations' to be distributed and are274 already explicitly excluding 'vicinity.integrations' via275 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,276 you can try to use `exclude_package_data`, or `include-package-data=False` in277 combination with a more fine grained `package-data` configuration.278279 You can read more about "package data files" on setuptools documentation page:280281 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html282283284 [^1]: For Python, any directory (with suitable naming) can be imported,285 even if it does not contain any `.py` files.286 On the other hand, currently there is no concept of package data287 directory, all directories are treated like packages.288 ********************************************************************************289290!!291 check.warn(importable)292copying vicinity/py.typed -> build/lib/vicinity293creating build/lib/vicinity/__pycache__294copying vicinity/__pycache__/version.cpython-314.pyc -> build/lib/vicinity/__pycache__295creating build/lib/vicinity/backends296copying vicinity/backends/__init__.py -> build/lib/vicinity/backends297copying vicinity/backends/annoy.py -> build/lib/vicinity/backends298copying vicinity/backends/base.py -> build/lib/vicinity/backends299copying vicinity/backends/basic.py -> build/lib/vicinity/backends300copying vicinity/backends/faiss.py -> build/lib/vicinity/backends301copying vicinity/backends/hnsw.py -> build/lib/vicinity/backends302copying vicinity/backends/pynndescent.py -> build/lib/vicinity/backends303copying vicinity/backends/usearch.py -> build/lib/vicinity/backends304copying vicinity/backends/voyager.py -> build/lib/vicinity/backends305creating build/lib/vicinity/integrations306copying vicinity/integrations/dataset_card_template.md -> build/lib/vicinity/integrations307copying vicinity/integrations/huggingface.py -> build/lib/vicinity/integrations308installing to build/bdist.linux-x86_64/wheel309running install310running install_lib311creating build/bdist.linux-x86_64/wheel312creating build/bdist.linux-x86_64/wheel/vicinity313copying build/lib/vicinity/datatypes.py -> build/bdist.linux-x86_64/wheel/./vicinity314copying build/lib/vicinity/utils.py -> build/bdist.linux-x86_64/wheel/./vicinity315copying build/lib/vicinity/__init__.py -> build/bdist.linux-x86_64/wheel/./vicinity316copying build/lib/vicinity/py.typed -> build/bdist.linux-x86_64/wheel/./vicinity317creating build/bdist.linux-x86_64/wheel/vicinity/integrations318copying build/lib/vicinity/integrations/dataset_card_template.md -> build/bdist.linux-x86_64/wheel/./vicinity/integrations319copying build/lib/vicinity/integrations/huggingface.py -> build/bdist.linux-x86_64/wheel/./vicinity/integrations320creating build/bdist.linux-x86_64/wheel/vicinity/backends321copying build/lib/vicinity/backends/pynndescent.py -> build/bdist.linux-x86_64/wheel/./vicinity/backends322copying build/lib/vicinity/backends/annoy.py -> build/bdist.linux-x86_64/wheel/./vicinity/backends323copying build/lib/vicinity/backends/basic.py -> build/bdist.linux-x86_64/wheel/./vicinity/backends324copying build/lib/vicinity/backends/base.py -> build/bdist.linux-x86_64/wheel/./vicinity/backends325copying build/lib/vicinity/backends/voyager.py -> build/bdist.linux-x86_64/wheel/./vicinity/backends326copying build/lib/vicinity/backends/hnsw.py -> build/bdist.linux-x86_64/wheel/./vicinity/backends327copying build/lib/vicinity/backends/faiss.py -> build/bdist.linux-x86_64/wheel/./vicinity/backends328copying build/lib/vicinity/backends/__init__.py -> build/bdist.linux-x86_64/wheel/./vicinity/backends329copying build/lib/vicinity/backends/usearch.py -> build/bdist.linux-x86_64/wheel/./vicinity/backends330copying build/lib/vicinity/vicinity.py -> build/bdist.linux-x86_64/wheel/./vicinity331creating build/bdist.linux-x86_64/wheel/vicinity/__pycache__332copying build/lib/vicinity/__pycache__/version.cpython-314.pyc -> build/bdist.linux-x86_64/wheel/./vicinity/__pycache__333copying build/lib/vicinity/version.py -> build/bdist.linux-x86_64/wheel/./vicinity334running install_egg_info335Copying vicinity.egg-info to build/bdist.linux-x86_64/wheel/./vicinity-0.4.4-py3.14.egg-info336running install_scripts337creating build/bdist.linux-x86_64/wheel/vicinity-0.4.4.dist-info/WHEEL338creating '/build/vicinity-0.4.4/dist/.tmp-duma2t2n/vicinity-0.4.4-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it339adding 'vicinity/__init__.py'340adding 'vicinity/datatypes.py'341adding 'vicinity/py.typed'342adding 'vicinity/utils.py'343adding 'vicinity/version.py'344adding 'vicinity/vicinity.py'345adding 'vicinity/__pycache__/version.cpython-314.pyc'346adding 'vicinity/backends/__init__.py'347adding 'vicinity/backends/annoy.py'348adding 'vicinity/backends/base.py'349adding 'vicinity/backends/basic.py'350adding 'vicinity/backends/faiss.py'351adding 'vicinity/backends/hnsw.py'352adding 'vicinity/backends/pynndescent.py'353adding 'vicinity/backends/usearch.py'354adding 'vicinity/backends/voyager.py'355adding 'vicinity/integrations/dataset_card_template.md'356adding 'vicinity/integrations/huggingface.py'357adding 'vicinity-0.4.4.dist-info/METADATA'358adding 'vicinity-0.4.4.dist-info/WHEEL'359adding 'vicinity-0.4.4.dist-info/top_level.txt'360adding 'vicinity-0.4.4.dist-info/RECORD'361removing build/bdist.linux-x86_64/wheel362Successfully built vicinity-0.4.4-py3-none-any.whl363Finished creating a wheel...364Finished executing pypaBuildPhasepythonRuntimeDepsCheckHook
365Executing pythonRuntimeDepsCheck366Checking runtime dependencies for vicinity-0.4.4-py3-none-any.whl367Finished executing pythonRuntimeDepsCheckinstallPhase
368Executing pypaInstallPhase369/nix/store/l33dp06nm8rsws9ay08sshbb0j31c8ly-python3.14-installer-1.0.1/lib/python3.14/site-packages/installer/__main__.py:118: RuntimeWarning: Skip installing vicinity/__pycache__/version.cpython-314.pyc from vicinity. Installing files in a __pycache__ directory poses a security risk. __pycache__ directories should not be included in wheels. This is probably an issue in the build process of 'vicinity'.370 installer.install(source, destination, {})371Successfully installed vicinity-0.4.4-py3-none-any.whl372Finished executing pypaInstallPhasepythonOutputDistPhase
373Executing pythonOutputDistPhase374Finished executing pythonOutputDistPhasefixupPhase
375shrinking RPATHs of ELF executables and libraries in /nix/store/kcjn4yh37l0zmpanki292wnk3ldjrpk4-python3.14-vicinity-0.4.4-dist376checking for references to /build/ in /nix/store/kcjn4yh37l0zmpanki292wnk3ldjrpk4-python3.14-vicinity-0.4.4-dist...377patching script interpreter paths in /nix/store/kcjn4yh37l0zmpanki292wnk3ldjrpk4-python3.14-vicinity-0.4.4-dist378shrinking RPATHs of ELF executables and libraries in /nix/store/kxnbb0h5ryfvvza41xvm3bk4j87arniq-python3.14-vicinity-0.4.4379checking for references to /build/ in /nix/store/kxnbb0h5ryfvvza41xvm3bk4j87arniq-python3.14-vicinity-0.4.4...380patching script interpreter paths in /nix/store/kxnbb0h5ryfvvza41xvm3bk4j87arniq-python3.14-vicinity-0.4.4381stripping (with command strip and flags -S -p) in /nix/store/kxnbb0h5ryfvvza41xvm3bk4j87arniq-python3.14-vicinity-0.4.4/lib382Executing pythonRemoveTestsDir383Finished executing pythonRemoveTestsDirpythonImportsCheckPhase
384Executing pythonImportsCheckPhase385Check whether the following modules can be imported: vicinitypythonMetadataCheckPhase
386Executing pythonMetadataCheckPhase