Sourcing python-remove-tests-dir-hook
Sourcing python-catch-conflicts-hook.sh
Sourcing python-remove-bin-bytecode-hook.sh
Sourcing pypa-build-hook
Using pypaBuildPhase
Sourcing python-runtime-deps-check-hook
Using pythonRuntimeDepsCheckHook
Sourcing pypa-install-hook
Using pypaInstallPhase
Sourcing python-imports-check-hook.sh
Using pythonImportsCheckPhase
Sourcing python-metadata-check-hook.sh
Using pythonMetadataCheckPhase
Sourcing python-namespaces-hook
Sourcing python-catch-conflicts-hook.sh
Using checkPhaseThreadLimitHook
Running phase: unpackPhase
unpacking source archive /nix/store/vcrp5i7fav7h0x98gqspihdrkwqb6710-vicinity-0.4.4.tar.gz
source root is vicinity-0.4.4
setting SOURCE_DATE_EPOCH to timestamp 1776179318 of file "vicinity-0.4.4/setup.cfg"
Running phase: patchPhase
Running phase: updateAutotoolsGnuConfigScriptsPhase
Running phase: configurePhase
no configure script, doing nothing
Running phase: buildPhase
Executing pypaBuildPhase
Including all tracked files automatically
Creating a wheel...
pypa build flags: --no-isolation --outdir dist/ --wheel
* Getting build dependencies for wheel...
/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]
version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set
When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.
Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.
  warnings.warn(
/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 deprecated
!!

        ********************************************************************************
        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).

        By 2027-Feb-18, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  corresp(dist, value, root_dir)
/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).
!!

        ********************************************************************************

        By 2027-Feb-18, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-files for details.
        ********************************************************************************

!!
  _apply_tool_table(dist, config, filename)
/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.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: MIT License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  dist._finalize_license_expression()
/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: MIT License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  self._finalize_license_expression()
running egg_info
writing vicinity.egg-info/PKG-INFO
writing dependency_links to vicinity.egg-info/dependency_links.txt
writing requirements to vicinity.egg-info/requires.txt
writing top-level names to vicinity.egg-info/top_level.txt
/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.
  return get_active_overrides().subprocess_timeout
reading manifest file 'vicinity.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'vicinity.egg-info/SOURCES.txt'
* Building wheel...
/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]
version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set
When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.
Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.
  warnings.warn(
/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 deprecated
!!

        ********************************************************************************
        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).

        By 2027-Feb-18, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  corresp(dist, value, root_dir)
/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).
!!

        ********************************************************************************

        By 2027-Feb-18, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-files for details.
        ********************************************************************************

!!
  _apply_tool_table(dist, config, filename)
/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.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: MIT License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  dist._finalize_license_expression()
/nix/store/6y5nmanp00gqfba9cmnsdaaiby99b266-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: MIT License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  self._finalize_license_expression()
running bdist_wheel
running build
running build_py
creating build/lib/vicinity
copying vicinity/version.py -> build/lib/vicinity
copying vicinity/__init__.py -> build/lib/vicinity
copying vicinity/datatypes.py -> build/lib/vicinity
copying vicinity/utils.py -> build/lib/vicinity
copying vicinity/vicinity.py -> build/lib/vicinity
running egg_info
writing vicinity.egg-info/PKG-INFO
writing dependency_links to vicinity.egg-info/dependency_links.txt
writing requirements to vicinity.egg-info/requires.txt
writing top-level names to vicinity.egg-info/top_level.txt
/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.
  return get_active_overrides().subprocess_timeout
reading manifest file 'vicinity.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'vicinity.egg-info/SOURCES.txt'
/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.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'vicinity.__pycache__' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'vicinity.__pycache__' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'vicinity.__pycache__' to be distributed and are
        already explicitly excluding 'vicinity.__pycache__' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

!!
  check.warn(importable)
/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.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'vicinity.backends' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'vicinity.backends' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'vicinity.backends' to be distributed and are
        already explicitly excluding 'vicinity.backends' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

!!
  check.warn(importable)
/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.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'vicinity.integrations' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'vicinity.integrations' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'vicinity.integrations' to be distributed and are
        already explicitly excluding 'vicinity.integrations' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


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

!!
  check.warn(importable)
copying vicinity/py.typed -> build/lib/vicinity
creating build/lib/vicinity/__pycache__
copying vicinity/__pycache__/version.cpython-314.pyc -> build/lib/vicinity/__pycache__
creating build/lib/vicinity/backends
copying vicinity/backends/__init__.py -> build/lib/vicinity/backends
copying vicinity/backends/annoy.py -> build/lib/vicinity/backends
copying vicinity/backends/base.py -> build/lib/vicinity/backends
copying vicinity/backends/basic.py -> build/lib/vicinity/backends
copying vicinity/backends/faiss.py -> build/lib/vicinity/backends
copying vicinity/backends/hnsw.py -> build/lib/vicinity/backends
copying vicinity/backends/pynndescent.py -> build/lib/vicinity/backends
copying vicinity/backends/usearch.py -> build/lib/vicinity/backends
copying vicinity/backends/voyager.py -> build/lib/vicinity/backends
creating build/lib/vicinity/integrations
copying vicinity/integrations/dataset_card_template.md -> build/lib/vicinity/integrations
copying vicinity/integrations/huggingface.py -> build/lib/vicinity/integrations
installing to build/bdist.macosx-14.0-arm64/wheel
running install
running install_lib
creating build/bdist.macosx-14.0-arm64/wheel
creating build/bdist.macosx-14.0-arm64/wheel/vicinity
copying build/lib/vicinity/version.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity
creating build/bdist.macosx-14.0-arm64/wheel/vicinity/backends
copying build/lib/vicinity/backends/pynndescent.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends
copying build/lib/vicinity/backends/usearch.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends
copying build/lib/vicinity/backends/voyager.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends
copying build/lib/vicinity/backends/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends
copying build/lib/vicinity/backends/faiss.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends
copying build/lib/vicinity/backends/hnsw.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends
copying build/lib/vicinity/backends/basic.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends
copying build/lib/vicinity/backends/base.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends
copying build/lib/vicinity/backends/annoy.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/backends
copying build/lib/vicinity/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity
creating build/bdist.macosx-14.0-arm64/wheel/vicinity/__pycache__
copying build/lib/vicinity/__pycache__/version.cpython-314.pyc -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/__pycache__
creating build/bdist.macosx-14.0-arm64/wheel/vicinity/integrations
copying build/lib/vicinity/integrations/dataset_card_template.md -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/integrations
copying build/lib/vicinity/integrations/huggingface.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity/integrations
copying build/lib/vicinity/datatypes.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity
copying build/lib/vicinity/utils.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity
copying build/lib/vicinity/py.typed -> build/bdist.macosx-14.0-arm64/wheel/./vicinity
copying build/lib/vicinity/vicinity.py -> build/bdist.macosx-14.0-arm64/wheel/./vicinity
running install_egg_info
Copying vicinity.egg-info to build/bdist.macosx-14.0-arm64/wheel/./vicinity-0.4.4-py3.14.egg-info
running install_scripts
creating build/bdist.macosx-14.0-arm64/wheel/vicinity-0.4.4.dist-info/WHEEL
creating '/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 it
adding 'vicinity/__init__.py'
adding 'vicinity/datatypes.py'
adding 'vicinity/py.typed'
adding 'vicinity/utils.py'
adding 'vicinity/version.py'
adding 'vicinity/vicinity.py'
adding 'vicinity/__pycache__/version.cpython-314.pyc'
adding 'vicinity/backends/__init__.py'
adding 'vicinity/backends/annoy.py'
adding 'vicinity/backends/base.py'
adding 'vicinity/backends/basic.py'
adding 'vicinity/backends/faiss.py'
adding 'vicinity/backends/hnsw.py'
adding 'vicinity/backends/pynndescent.py'
adding 'vicinity/backends/usearch.py'
adding 'vicinity/backends/voyager.py'
adding 'vicinity/integrations/dataset_card_template.md'
adding 'vicinity/integrations/huggingface.py'
adding 'vicinity-0.4.4.dist-info/METADATA'
adding 'vicinity-0.4.4.dist-info/WHEEL'
adding 'vicinity-0.4.4.dist-info/top_level.txt'
adding 'vicinity-0.4.4.dist-info/RECORD'
removing build/bdist.macosx-14.0-arm64/wheel
Successfully built vicinity-0.4.4-py3-none-any.whl
Finished creating a wheel...
Finished executing pypaBuildPhase
Running phase: pythonRuntimeDepsCheckHook
Executing pythonRuntimeDepsCheck
Checking runtime dependencies for vicinity-0.4.4-py3-none-any.whl
Finished executing pythonRuntimeDepsCheck
Running phase: installPhase
Executing pypaInstallPhase
/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'.
  installer.install(source, destination, {})
Successfully installed vicinity-0.4.4-py3-none-any.whl
Finished executing pypaInstallPhase
Running phase: pythonOutputDistPhase
Executing pythonOutputDistPhase
Finished executing pythonOutputDistPhase
Running phase: fixupPhase
checking for references to /nix/var/nix/builds/nix-41294-3620735172/ in /nix/store/xi63779wdcy2kji8gnd7bh255gbcmmjk-python3.14-vicinity-0.4.4...
patching script interpreter paths in /nix/store/xi63779wdcy2kji8gnd7bh255gbcmmjk-python3.14-vicinity-0.4.4
stripping (with command strip and flags -S) in  /nix/store/xi63779wdcy2kji8gnd7bh255gbcmmjk-python3.14-vicinity-0.4.4/lib
checking for references to /nix/var/nix/builds/nix-41294-3620735172/ in /nix/store/65a6kw2ky1ggfqn2xlr11kjca7yd0jlc-python3.14-vicinity-0.4.4-dist...
patching script interpreter paths in /nix/store/65a6kw2ky1ggfqn2xlr11kjca7yd0jlc-python3.14-vicinity-0.4.4-dist
Executing pythonRemoveTestsDir
Finished executing pythonRemoveTestsDir
Running phase: pythonCatchConflictsPhase
Running phase: pythonRemoveBinBytecodePhase
Running phase: pythonImportsCheckPhase
Executing pythonImportsCheckPhase
Check whether the following modules can be imported: vicinity
Running phase: pythonMetadataCheckPhase
Executing pythonMetadataCheckPhase