python3.14-vicinity-0.4.4
aarch64-darwin.pkgs-semble
· build #1911
· raw
1Sourcing python-remove-tests-dir-hook2Sourcing python-catch-conflicts-hook.sh3Sourcing python-remove-bin-bytecode-hook.sh4Sourcing pypa-build-hook5Using pypaBuildPhase6Sourcing python-runtime-deps-check-hook7Using pythonRuntimeDepsCheckHook8Sourcing pypa-install-hook9Using pypaInstallPhase10Sourcing python-imports-check-hook.sh11Using pythonImportsCheckPhase12Sourcing python-metadata-check-hook.sh13Using pythonMetadataCheckPhase14Sourcing python-namespaces-hook15Sourcing python-catch-conflicts-hook.sh16Using checkPhaseThreadLimitHook
unpackPhase
17unpacking source archive /nix/store/vcrp5i7fav7h0x98gqspihdrkwqb6710-vicinity-0.4.4.tar.gz18source root is vicinity-0.4.419setting SOURCE_DATE_EPOCH to timestamp 1776179318 of file "vicinity-0.4.4/setup.cfg"configurePhase
20no configure script, doing nothingbuildPhase
21Executing pypaBuildPhase22Including all tracked files automatically23Creating a wheel...24pypa build flags: --no-isolation --outdir dist/ --wheel25* Getting build dependencies for wheel...26/nix/store/8595imhlywqdam3lnc1hqy7l4v47ksna-python3.14-setuptools-scm-10.0.5/lib/python3.14/site-packages/setuptools_scm/_integration/deprecation.py:7: UserWarning: pyproject.toml: at [tool.setuptools.dynamic]27version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set28When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.29Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.30 warnings.warn(31/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-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 deprecated32!!3334 ********************************************************************************35 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).3637 By 2027-Feb-18, you need to update your project and remove deprecated calls38 or your builds will no longer be supported.3940 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.41 ********************************************************************************4243!!44 corresp(dist, value, root_dir)45/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-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).46!!4748 ********************************************************************************4950 By 2027-Feb-18, you need to update your project and remove deprecated calls51 or your builds will no longer be supported.5253 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-files for details.54 ********************************************************************************5556!!57 _apply_tool_table(dist, config, filename)58/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated.59!!6061 ********************************************************************************62 Please consider removing the following classifiers in favor of a SPDX license expression:6364 License :: OSI Approved :: MIT License6566 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.67 ********************************************************************************6869!!70 dist._finalize_license_expression()71/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.72!!7374 ********************************************************************************75 Please consider removing the following classifiers in favor of a SPDX license expression:7677 License :: OSI Approved :: MIT License7879 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.80 ********************************************************************************8182!!83 self._finalize_license_expression()84running egg_info85writing vicinity.egg-info/PKG-INFO86writing dependency_links to vicinity.egg-info/dependency_links.txt87writing requirements to vicinity.egg-info/requires.txt88writing top-level names to vicinity.egg-info/top_level.txt89/nix/store/rpaf3mcah7ha3piyki98mspd4vvm2p2m-python3.14-vcs-versioning-1.1.1/lib/python3.14/site-packages/vcs_versioning/overrides.py:609: UserWarning: No GlobalOverrides context is active. Auto-creating one with SETUPTOOLS_SCM prefix for backwards compatibility. Consider using 'with GlobalOverrides.from_env("YOUR_TOOL"):' explicitly.90 return get_active_overrides().subprocess_timeout91reading manifest file 'vicinity.egg-info/SOURCES.txt'92reading manifest template 'MANIFEST.in'93writing manifest file 'vicinity.egg-info/SOURCES.txt'94* Building wheel...95/nix/store/8595imhlywqdam3lnc1hqy7l4v47ksna-python3.14-setuptools-scm-10.0.5/lib/python3.14/site-packages/setuptools_scm/_integration/deprecation.py:7: UserWarning: pyproject.toml: at [tool.setuptools.dynamic]96version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set97When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.98Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.99 warnings.warn(100/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-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 deprecated101!!102103 ********************************************************************************104 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).105106 By 2027-Feb-18, you need to update your project and remove deprecated calls107 or your builds will no longer be supported.108109 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.110 ********************************************************************************111112!!113 corresp(dist, value, root_dir)114/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-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).115!!116117 ********************************************************************************118119 By 2027-Feb-18, you need to update your project and remove deprecated calls120 or your builds will no longer be supported.121122 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-files for details.123 ********************************************************************************124125!!126 _apply_tool_table(dist, config, filename)127/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated.128!!129130 ********************************************************************************131 Please consider removing the following classifiers in favor of a SPDX license expression:132133 License :: OSI Approved :: MIT License134135 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.136 ********************************************************************************137138!!139 dist._finalize_license_expression()140/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.141!!142143 ********************************************************************************144 Please consider removing the following classifiers in favor of a SPDX license expression:145146 License :: OSI Approved :: MIT License147148 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.149 ********************************************************************************150151!!152 self._finalize_license_expression()153running bdist_wheel154running build155running build_py156creating build/lib/vicinity157copying vicinity/version.py -> build/lib/vicinity158copying vicinity/__init__.py -> build/lib/vicinity159copying vicinity/datatypes.py -> build/lib/vicinity160copying vicinity/utils.py -> build/lib/vicinity161copying vicinity/vicinity.py -> build/lib/vicinity162running egg_info163writing vicinity.egg-info/PKG-INFO164writing dependency_links to vicinity.egg-info/dependency_links.txt165writing requirements to vicinity.egg-info/requires.txt166writing top-level names to vicinity.egg-info/top_level.txt167/nix/store/rpaf3mcah7ha3piyki98mspd4vvm2p2m-python3.14-vcs-versioning-1.1.1/lib/python3.14/site-packages/vcs_versioning/overrides.py:609: UserWarning: No GlobalOverrides context is active. Auto-creating one with SETUPTOOLS_SCM prefix for backwards compatibility. Consider using 'with GlobalOverrides.from_env("YOUR_TOOL"):' explicitly.168 return get_active_overrides().subprocess_timeout169reading manifest file 'vicinity.egg-info/SOURCES.txt'170reading manifest template 'MANIFEST.in'171writing manifest file 'vicinity.egg-info/SOURCES.txt'172/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-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.173!!174175 ********************************************************************************176 ############################177 # Package would be ignored #178 ############################179 Python recognizes 'vicinity.__pycache__' as an importable package[^1],180 but it is absent from setuptools' `packages` configuration.181182 This leads to an ambiguous overall configuration. If you want to distribute this183 package, please make sure that 'vicinity.__pycache__' is explicitly added184 to the `packages` configuration field.185186 Alternatively, you can also rely on setuptools' discovery methods187 (for example by using `find_namespace_packages(...)`/`find_namespace:`188 instead of `find_packages(...)`/`find:`).189190 You can read more about "package discovery" on setuptools documentation page:191192 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html193194 If you don't want 'vicinity.__pycache__' to be distributed and are195 already explicitly excluding 'vicinity.__pycache__' via196 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,197 you can try to use `exclude_package_data`, or `include-package-data=False` in198 combination with a more fine grained `package-data` configuration.199200 You can read more about "package data files" on setuptools documentation page:201202 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html203204205 [^1]: For Python, any directory (with suitable naming) can be imported,206 even if it does not contain any `.py` files.207 On the other hand, currently there is no concept of package data208 directory, all directories are treated like packages.209 ********************************************************************************210211!!212 check.warn(importable)213/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-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.214!!215216 ********************************************************************************217 ############################218 # Package would be ignored #219 ############################220 Python recognizes 'vicinity.backends' as an importable package[^1],221 but it is absent from setuptools' `packages` configuration.222223 This leads to an ambiguous overall configuration. If you want to distribute this224 package, please make sure that 'vicinity.backends' is explicitly added225 to the `packages` configuration field.226227 Alternatively, you can also rely on setuptools' discovery methods228 (for example by using `find_namespace_packages(...)`/`find_namespace:`229 instead of `find_packages(...)`/`find:`).230231 You can read more about "package discovery" on setuptools documentation page:232233 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html234235 If you don't want 'vicinity.backends' to be distributed and are236 already explicitly excluding 'vicinity.backends' via237 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,238 you can try to use `exclude_package_data`, or `include-package-data=False` in239 combination with a more fine grained `package-data` configuration.240241 You can read more about "package data files" on setuptools documentation page:242243 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html244245246 [^1]: For Python, any directory (with suitable naming) can be imported,247 even if it does not contain any `.py` files.248 On the other hand, currently there is no concept of package data249 directory, all directories are treated like packages.250 ********************************************************************************251252!!253 check.warn(importable)254/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-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.255!!256257 ********************************************************************************258 ############################259 # Package would be ignored #260 ############################261 Python recognizes 'vicinity.integrations' as an importable package[^1],262 but it is absent from setuptools' `packages` configuration.263264 This leads to an ambiguous overall configuration. If you want to distribute this265 package, please make sure that 'vicinity.integrations' is explicitly added266 to the `packages` configuration field.267268 Alternatively, you can also rely on setuptools' discovery methods269 (for example by using `find_namespace_packages(...)`/`find_namespace:`270 instead of `find_packages(...)`/`find:`).271272 You can read more about "package discovery" on setuptools documentation page:273274 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html275276 If you don't want 'vicinity.integrations' to be distributed and are277 already explicitly excluding 'vicinity.integrations' via278 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,279 you can try to use `exclude_package_data`, or `include-package-data=False` in280 combination with a more fine grained `package-data` configuration.281282 You can read more about "package data files" on setuptools documentation page:283284 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html285286287 [^1]: For Python, any directory (with suitable naming) can be imported,288 even if it does not contain any `.py` files.289 On the other hand, currently there is no concept of package data290 directory, all directories are treated like packages.291 ********************************************************************************292293!!294 check.warn(importable)295copying vicinity/py.typed -> build/lib/vicinity296creating build/lib/vicinity/__pycache__297copying vicinity/__pycache__/version.cpython-314.pyc -> build/lib/vicinity/__pycache__298creating build/lib/vicinity/backends299copying vicinity/backends/__init__.py -> build/lib/vicinity/backends300copying vicinity/backends/annoy.py -> build/lib/vicinity/backends301copying vicinity/backends/base.py -> build/lib/vicinity/backends302copying vicinity/backends/basic.py -> build/lib/vicinity/backends303copying vicinity/backends/faiss.py -> build/lib/vicinity/backends304copying vicinity/backends/hnsw.py -> build/lib/vicinity/backends305copying vicinity/backends/pynndescent.py -> build/lib/vicinity/backends306copying vicinity/backends/usearch.py -> build/lib/vicinity/backends307copying vicinity/backends/voyager.py -> build/lib/vicinity/backends308creating build/lib/vicinity/integrations309copying vicinity/integrations/dataset_card_template.md -> build/lib/vicinity/integrations310copying vicinity/integrations/huggingface.py -> build/lib/vicinity/integrations311installing to build/bdist.macosx-14.0-arm64/wheel312running install313running install_lib314creating build/bdist.macosx-14.0-arm64/wheel315creating build/bdist.macosx-14.0-arm64/wheel/vicinity316copying build/lib/vicinity/version.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity317creating build/bdist.macosx-14.0-arm64/wheel/vicinity/backends318copying build/lib/vicinity/backends/pynndescent.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends319copying build/lib/vicinity/backends/usearch.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends320copying build/lib/vicinity/backends/voyager.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends321copying build/lib/vicinity/backends/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends322copying build/lib/vicinity/backends/faiss.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends323copying build/lib/vicinity/backends/hnsw.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends324copying build/lib/vicinity/backends/basic.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends325copying build/lib/vicinity/backends/base.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends326copying build/lib/vicinity/backends/annoy.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends327copying build/lib/vicinity/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity328creating build/bdist.macosx-14.0-arm64/wheel/vicinity/__pycache__329copying build/lib/vicinity/__pycache__/version.cpython-314.pyc -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/__pycache__330creating build/bdist.macosx-14.0-arm64/wheel/vicinity/integrations331copying build/lib/vicinity/integrations/dataset_card_template.md -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/integrations332copying build/lib/vicinity/integrations/huggingface.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/integrations333copying build/lib/vicinity/datatypes.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity334copying build/lib/vicinity/utils.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity335copying build/lib/vicinity/py.typed -> build/bdist.macosx-14.0-arm64/wheel/./vicinity336copying build/lib/vicinity/vicinity.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity337running install_egg_info338Copying vicinity.egg-info to build/bdist.macosx-14.0-arm64/wheel/./vicinity-0.4.4-py3.14.egg-info339running install_scripts340creating build/bdist.macosx-14.0-arm64/wheel/vicinity-0.4.4.dist-info/WHEEL341creating '/nix/var/nix/builds/nix-41294-3620735172/vicinity-0.4.4/dist/.tmp-_qdxez01/vicinity-0.4.4-py3-none-any.whl' and adding 'build/bdist.macosx-14.0-arm64/wheel' to it342adding 'vicinity/__init__.py'343adding 'vicinity/datatypes.py'344adding 'vicinity/py.typed'345adding 'vicinity/utils.py'346adding 'vicinity/version.py'347adding 'vicinity/vicinity.py'348adding 'vicinity/__pycache__/version.cpython-314.pyc'349adding 'vicinity/backends/__init__.py'350adding 'vicinity/backends/annoy.py'351adding 'vicinity/backends/base.py'352adding 'vicinity/backends/basic.py'353adding 'vicinity/backends/faiss.py'354adding 'vicinity/backends/hnsw.py'355adding 'vicinity/backends/pynndescent.py'356adding 'vicinity/backends/usearch.py'357adding 'vicinity/backends/voyager.py'358adding 'vicinity/integrations/dataset_card_template.md'359adding 'vicinity/integrations/huggingface.py'360adding 'vicinity-0.4.4.dist-info/METADATA'361adding 'vicinity-0.4.4.dist-info/WHEEL'362adding 'vicinity-0.4.4.dist-info/top_level.txt'363adding 'vicinity-0.4.4.dist-info/RECORD'364removing build/bdist.macosx-14.0-arm64/wheel365Successfully built vicinity-0.4.4-py3-none-any.whl366Finished creating a wheel...367Finished executing pypaBuildPhasepythonRuntimeDepsCheckHook
368Executing pythonRuntimeDepsCheck369Checking runtime dependencies for vicinity-0.4.4-py3-none-any.whl370Finished executing pythonRuntimeDepsCheckinstallPhase
371Executing pypaInstallPhase372/nix/store/07l852hvsilx9kx08f8h2zf6acqa21yb-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'.373 installer.install(source, destination, {})374Successfully installed vicinity-0.4.4-py3-none-any.whl375Finished executing pypaInstallPhasepythonOutputDistPhase
376Executing pythonOutputDistPhase377Finished executing pythonOutputDistPhasefixupPhase
378checking for references to /nix/var/nix/builds/nix-41294-3620735172/ in /nix/store/xi63779wdcy2kji8gnd7bh255gbcmmjk-python3.14-vicinity-0.4.4...379patching script interpreter paths in /nix/store/xi63779wdcy2kji8gnd7bh255gbcmmjk-python3.14-vicinity-0.4.4380stripping (with command strip and flags -S) in /nix/store/xi63779wdcy2kji8gnd7bh255gbcmmjk-python3.14-vicinity-0.4.4/lib381checking for references to /nix/var/nix/builds/nix-41294-3620735172/ in /nix/store/65a6kw2ky1ggfqn2xlr11kjca7yd0jlc-python3.14-vicinity-0.4.4-dist...382patching script interpreter paths in /nix/store/65a6kw2ky1ggfqn2xlr11kjca7yd0jlc-python3.14-vicinity-0.4.4-dist383Executing pythonRemoveTestsDir384Finished executing pythonRemoveTestsDirpythonImportsCheckPhase
385Executing pythonImportsCheckPhase386Check whether the following modules can be imported: vicinitypythonMetadataCheckPhase
387Executing pythonMetadataCheckPhase