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/92g9pabzi3dln34156xq8aca3p0ivzbr-model2vec-0.8.1.tar.gz source root is model2vec-0.8.1 setting SOURCE_DATE_EPOCH to timestamp 1774618707 of file "model2vec-0.8.1/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 model2vec.egg-info/PKG-INFO writing dependency_links to model2vec.egg-info/dependency_links.txt writing requirements to model2vec.egg-info/requires.txt writing top-level names to model2vec.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 'model2vec.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'model2vec.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/model2vec copying model2vec/version.py -> build/lib/model2vec copying model2vec/vocabulary_quantization.py -> build/lib/model2vec copying model2vec/quantization.py -> build/lib/model2vec copying model2vec/__init__.py -> build/lib/model2vec copying model2vec/model.py -> build/lib/model2vec copying model2vec/utils.py -> build/lib/model2vec running egg_info writing model2vec.egg-info/PKG-INFO writing dependency_links to model2vec.egg-info/dependency_links.txt writing requirements to model2vec.egg-info/requires.txt writing top-level names to model2vec.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 'model2vec.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'model2vec.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 'model2vec.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'model2vec.__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 'model2vec.__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 'model2vec.__pycache__' to be distributed and are already explicitly excluding 'model2vec.__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 'model2vec.distill' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'model2vec.distill' 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 'model2vec.distill' 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 'model2vec.distill' to be distributed and are already explicitly excluding 'model2vec.distill' 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 'model2vec.inference' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'model2vec.inference' 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 'model2vec.inference' 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 'model2vec.inference' to be distributed and are already explicitly excluding 'model2vec.inference' 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 'model2vec.modelcards' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'model2vec.modelcards' 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 'model2vec.modelcards' 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 'model2vec.modelcards' to be distributed and are already explicitly excluding 'model2vec.modelcards' 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 'model2vec.persistence' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'model2vec.persistence' 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 'model2vec.persistence' 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 'model2vec.persistence' to be distributed and are already explicitly excluding 'model2vec.persistence' 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 'model2vec.tokenizer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'model2vec.tokenizer' 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 'model2vec.tokenizer' 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 'model2vec.tokenizer' to be distributed and are already explicitly excluding 'model2vec.tokenizer' 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 'model2vec.train' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'model2vec.train' 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 'model2vec.train' 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 'model2vec.train' to be distributed and are already explicitly excluding 'model2vec.train' 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 model2vec/py.typed -> build/lib/model2vec creating build/lib/model2vec/__pycache__ copying model2vec/__pycache__/version.cpython-314.pyc -> build/lib/model2vec/__pycache__ creating build/lib/model2vec/distill copying model2vec/distill/__init__.py -> build/lib/model2vec/distill copying model2vec/distill/distillation.py -> build/lib/model2vec/distill copying model2vec/distill/inference.py -> build/lib/model2vec/distill copying model2vec/distill/utils.py -> build/lib/model2vec/distill creating build/lib/model2vec/inference copying model2vec/inference/README.md -> build/lib/model2vec/inference copying model2vec/inference/__init__.py -> build/lib/model2vec/inference copying model2vec/inference/model.py -> build/lib/model2vec/inference creating build/lib/model2vec/modelcards copying model2vec/modelcards/__init__.py -> build/lib/model2vec/modelcards copying model2vec/modelcards/classifier_template.md -> build/lib/model2vec/modelcards copying model2vec/modelcards/model_card_template.md -> build/lib/model2vec/modelcards copying model2vec/modelcards/modelcards.py -> build/lib/model2vec/modelcards creating build/lib/model2vec/persistence copying model2vec/persistence/__init__.py -> build/lib/model2vec/persistence copying model2vec/persistence/datamodels.py -> build/lib/model2vec/persistence copying model2vec/persistence/hf.py -> build/lib/model2vec/persistence copying model2vec/persistence/persistence.py -> build/lib/model2vec/persistence creating build/lib/model2vec/tokenizer copying model2vec/tokenizer/__init__.py -> build/lib/model2vec/tokenizer copying model2vec/tokenizer/tokenizer.py -> build/lib/model2vec/tokenizer creating build/lib/model2vec/train copying model2vec/train/README.md -> build/lib/model2vec/train copying model2vec/train/__init__.py -> build/lib/model2vec/train copying model2vec/train/base.py -> build/lib/model2vec/train copying model2vec/train/classifier.py -> build/lib/model2vec/train copying model2vec/train/utils.py -> build/lib/model2vec/train 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/model2vec copying build/lib/model2vec/version.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec copying build/lib/model2vec/vocabulary_quantization.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec copying build/lib/model2vec/quantization.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec creating build/bdist.macosx-14.0-arm64/wheel/model2vec/tokenizer copying build/lib/model2vec/tokenizer/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/tokenizer copying build/lib/model2vec/tokenizer/tokenizer.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/tokenizer copying build/lib/model2vec/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec creating build/bdist.macosx-14.0-arm64/wheel/model2vec/distill copying build/lib/model2vec/distill/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/distill copying build/lib/model2vec/distill/utils.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/distill copying build/lib/model2vec/distill/inference.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/distill copying build/lib/model2vec/distill/distillation.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/distill creating build/bdist.macosx-14.0-arm64/wheel/model2vec/__pycache__ copying build/lib/model2vec/__pycache__/version.cpython-314.pyc -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/__pycache__ copying build/lib/model2vec/model.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec copying build/lib/model2vec/utils.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec creating build/bdist.macosx-14.0-arm64/wheel/model2vec/persistence copying build/lib/model2vec/persistence/persistence.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/persistence copying build/lib/model2vec/persistence/datamodels.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/persistence copying build/lib/model2vec/persistence/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/persistence copying build/lib/model2vec/persistence/hf.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/persistence creating build/bdist.macosx-14.0-arm64/wheel/model2vec/modelcards copying build/lib/model2vec/modelcards/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/modelcards copying build/lib/model2vec/modelcards/classifier_template.md -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/modelcards copying build/lib/model2vec/modelcards/modelcards.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/modelcards copying build/lib/model2vec/modelcards/model_card_template.md -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/modelcards creating build/bdist.macosx-14.0-arm64/wheel/model2vec/train copying build/lib/model2vec/train/classifier.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/train copying build/lib/model2vec/train/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/train copying build/lib/model2vec/train/README.md -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/train copying build/lib/model2vec/train/utils.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/train copying build/lib/model2vec/train/base.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/train copying build/lib/model2vec/py.typed -> build/bdist.macosx-14.0-arm64/wheel/./model2vec creating build/bdist.macosx-14.0-arm64/wheel/model2vec/inference copying build/lib/model2vec/inference/__init__.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/inference copying build/lib/model2vec/inference/model.py -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/inference copying build/lib/model2vec/inference/README.md -> build/bdist.macosx-14.0-arm64/wheel/./model2vec/inference running install_egg_info Copying model2vec.egg-info to build/bdist.macosx-14.0-arm64/wheel/./model2vec-0.8.1-py3.14.egg-info running install_scripts creating build/bdist.macosx-14.0-arm64/wheel/model2vec-0.8.1.dist-info/WHEEL creating '/nix/var/nix/builds/nix-74020-523108159/model2vec-0.8.1/dist/.tmp-u2t42yfm/model2vec-0.8.1-py3-none-any.whl' and adding 'build/bdist.macosx-14.0-arm64/wheel' to it adding 'model2vec/__init__.py' adding 'model2vec/model.py' adding 'model2vec/py.typed' adding 'model2vec/quantization.py' adding 'model2vec/utils.py' adding 'model2vec/version.py' adding 'model2vec/vocabulary_quantization.py' adding 'model2vec/__pycache__/version.cpython-314.pyc' adding 'model2vec/distill/__init__.py' adding 'model2vec/distill/distillation.py' adding 'model2vec/distill/inference.py' adding 'model2vec/distill/utils.py' adding 'model2vec/inference/README.md' adding 'model2vec/inference/__init__.py' adding 'model2vec/inference/model.py' adding 'model2vec/modelcards/__init__.py' adding 'model2vec/modelcards/classifier_template.md' adding 'model2vec/modelcards/model_card_template.md' adding 'model2vec/modelcards/modelcards.py' adding 'model2vec/persistence/__init__.py' adding 'model2vec/persistence/datamodels.py' adding 'model2vec/persistence/hf.py' adding 'model2vec/persistence/persistence.py' adding 'model2vec/tokenizer/__init__.py' adding 'model2vec/tokenizer/tokenizer.py' adding 'model2vec/train/README.md' adding 'model2vec/train/__init__.py' adding 'model2vec/train/base.py' adding 'model2vec/train/classifier.py' adding 'model2vec/train/utils.py' adding 'model2vec-0.8.1.dist-info/METADATA' adding 'model2vec-0.8.1.dist-info/WHEEL' adding 'model2vec-0.8.1.dist-info/top_level.txt' adding 'model2vec-0.8.1.dist-info/RECORD' removing build/bdist.macosx-14.0-arm64/wheel Successfully built model2vec-0.8.1-py3-none-any.whl Finished creating a wheel... Finished executing pypaBuildPhase Running phase: pythonRuntimeDepsCheckHook Executing pythonRuntimeDepsCheck Checking runtime dependencies for model2vec-0.8.1-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 model2vec/__pycache__/version.cpython-314.pyc from model2vec. 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 'model2vec'. installer.install(source, destination, {}) Successfully installed model2vec-0.8.1-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-74020-523108159/ in /nix/store/m6r8c2s1qvqgffhmlzab9z5ma5g0yg17-python3.14-model2vec-0.8.1... patching script interpreter paths in /nix/store/m6r8c2s1qvqgffhmlzab9z5ma5g0yg17-python3.14-model2vec-0.8.1 stripping (with command strip and flags -S) in /nix/store/m6r8c2s1qvqgffhmlzab9z5ma5g0yg17-python3.14-model2vec-0.8.1/lib checking for references to /nix/var/nix/builds/nix-74020-523108159/ in /nix/store/1cydz0r6a7jxwrxiimgflsw1ywzbwsr8-python3.14-model2vec-0.8.1-dist... patching script interpreter paths in /nix/store/1cydz0r6a7jxwrxiimgflsw1ywzbwsr8-python3.14-model2vec-0.8.1-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: model2vec Running phase: pythonMetadataCheckPhase Executing pythonMetadataCheckPhase