Open
Description
Hi
I am not able to install spacy-layout. I get the following error when I run this pip install spacy-layout in my MacOS machine (Mac M1 Pro).
On a google search, this is the closest I could get but it didn't help me unfortunately.
Would anyone know how to resolve this issue?
Note: I shortened the output by a bit otherwise Github wouldn't let me publish.
Collecting spacy-layout
Using cached spacy_layout-0.0.7-py2.py3-none-any.whl.metadata (10 kB)
Collecting spacy>=3.7.5 (from spacy-layout)
Using cached spacy-3.8.2.tar.gz (1.3 MB)
Installing build dependencies ... error
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [707 lines of output]
Ignoring numpy: markers 'python_version < "3.9"' don't match your environment
Collecting setuptools
Using cached setuptools-75.6.0-py3-none-any.whl.metadata (6.7 kB)
Collecting cython<3.0,>=0.25
Using cached Cython-0.29.37-py2.py3-none-any.whl.metadata (3.1 kB)
Collecting cymem<2.1.0,>=2.0.2
Using cached cymem-2.0.10-cp313-cp313-macosx_11_0_arm64.whl.metadata (8.4 kB)
Collecting preshed<3.1.0,>=3.0.2
Using cached preshed-3.0.9-cp313-cp313-macosx_14_0_arm64.whl
Collecting murmurhash<1.1.0,>=0.28.0
Using cached murmurhash-1.0.11-cp313-cp313-macosx_11_0_arm64.whl.metadata (2.0 kB)
Collecting thinc<8.4.0,>=8.3.0
Using cached thinc-8.3.2.tar.gz (193 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting numpy<2.1.0,>=2.0.0
Using cached numpy-2.0.2-cp313-cp313-macosx_14_0_arm64.whl
Collecting blis<1.1.0,>=1.0.0 (from thinc<8.4.0,>=8.3.0)
Using cached blis-1.0.1-cp313-cp313-macosx_14_0_arm64.whl
Collecting wasabi<1.2.0,>=0.8.1 (from thinc<8.4.0,>=8.3.0)
Using cached wasabi-1.1.3-py3-none-any.whl.metadata (28 kB)
Collecting srsly<3.0.0,>=2.4.0 (from thinc<8.4.0,>=8.3.0)
Using cached srsly-2.4.8.tar.gz (351 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting catalogue<2.1.0,>=2.0.4 (from thinc<8.4.0,>=8.3.0)
Using cached catalogue-2.0.10-py3-none-any.whl.metadata (14 kB)
Collecting confection<1.0.0,>=0.0.1 (from thinc<8.4.0,>=8.3.0)
Using cached confection-0.1.5-py3-none-any.whl.metadata (19 kB)
Collecting pydantic!=1.8,!=1.8.1,<3.0.0,>=1.7.4 (from thinc<8.4.0,>=8.3.0)
Using cached pydantic-2.10.2-py3-none-any.whl.metadata (170 kB)
Collecting packaging>=20.0 (from thinc<8.4.0,>=8.3.0)
Using cached packaging-24.2-py3-none-any.whl.metadata (3.2 kB)
Collecting annotated-types>=0.6.0 (from pydantic!=1.8,!=1.8.1,<3.0.0,>=1.7.4->thinc<8.4.0,>=8.3.0)
Using cached annotated_types-0.7.0-py3-none-any.whl.metadata (15 kB)
Collecting pydantic-core==2.27.1 (from pydantic!=1.8,!=1.8.1,<3.0.0,>=1.7.4->thinc<8.4.0,>=8.3.0)
Using cached pydantic_core-2.27.1-cp313-cp313-macosx_11_0_arm64.whl.metadata (6.6 kB)
Collecting typing-extensions>=4.12.2 (from pydantic!=1.8,!=1.8.1,<3.0.0,>=1.7.4->thinc<8.4.0,>=8.3.0)
Using cached typing_extensions-4.12.2-py3-none-any.whl.metadata (3.0 kB)
Using cached setuptools-75.6.0-py3-none-any.whl (1.2 MB)
Using cached Cython-0.29.37-py2.py3-none-any.whl (989 kB)
Using cached cymem-2.0.10-cp313-cp313-macosx_11_0_arm64.whl (41 kB)
Using cached murmurhash-1.0.11-cp313-cp313-macosx_11_0_arm64.whl (26 kB)
Using cached catalogue-2.0.10-py3-none-any.whl (17 kB)
Using cached confection-0.1.5-py3-none-any.whl (35 kB)
Using cached packaging-24.2-py3-none-any.whl (65 kB)
Using cached pydantic-2.10.2-py3-none-any.whl (456 kB)
Using cached pydantic_core-2.27.1-cp313-cp313-macosx_11_0_arm64.whl (1.8 MB)
Using cached wasabi-1.1.3-py3-none-any.whl (27 kB)
Using cached annotated_types-0.7.0-py3-none-any.whl (13 kB)
Using cached typing_extensions-4.12.2-py3-none-any.whl (37 kB)
Building wheels for collected packages: thinc, srsly
Building wheel for thinc (pyproject.toml): started
Building wheel for thinc (pyproject.toml): finished with status 'error'
error: subprocess-exited-with-error
× Building wheel for thinc (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [371 lines of output]
Cythonizing sources
running bdist_wheel
running build
running build_py
creating build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/config.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/compat.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/util.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/__init__.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/mypy.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/types.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/about.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/model.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/optimizers.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/api.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/loss.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/initializers.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/schedules.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc
creating build/lib.macosx-14.0-arm64-cpython-313/thinc/layers
copying thinc/layers/remap_ids.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/layers
copying thinc/layers/with_debug.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/layers
copying thinc/layers/mxnetwrapper.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/layers
copying thinc/layers/siamese.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/layers
.
.
.
creating build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/modules
copying thinc/tests/mypy/modules/fail_no_plugin.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/modules
copying thinc/tests/mypy/modules/success_no_plugin.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/modules
copying thinc/tests/mypy/modules/fail_plugin.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/modules
copying thinc/tests/mypy/modules/__init__.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/modules
copying thinc/tests/mypy/modules/success_plugin.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/modules
creating build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/regression/issue519
copying thinc/tests/regression/issue519/test_issue519.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/regression/issue519
copying thinc/tests/regression/issue519/__init__.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/regression/issue519
copying thinc/tests/regression/issue519/program.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/regression/issue519
creating build/lib.macosx-14.0-arm64-cpython-313/thinc/extra/tests
copying thinc/extra/tests/__init__.py -> build/lib.macosx-14.0-arm64-cpython-313/thinc/extra/tests
running egg_info
writing thinc.egg-info/PKG-INFO
writing dependency_links to thinc.egg-info/dependency_links.txt
writing entry points to thinc.egg-info/entry_points.txt
writing requirements to thinc.egg-info/requires.txt
writing top-level names to thinc.egg-info/top_level.txt
dependency /opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/Python.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/arrayobject.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/arrayscalars.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/ndarrayobject.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/ndarraytypes.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/ufuncobject.h won't be automatically included in the manifest: the path must be relative
dependency /opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/Python.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/arrayobject.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/arrayscalars.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/ndarrayobject.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/ndarraytypes.h won't be automatically included in the manifest: the path must be relative
dependency /private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include/numpy/ufuncobject.h won't be automatically included in the manifest: the path must be relative
reading manifest file 'thinc.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'tmp'
adding license file 'LICENSE'
writing manifest file 'thinc.egg-info/SOURCES.txt'
/private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'thinc.tests.mypy.configs' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'thinc.tests.mypy.configs' 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 'thinc.tests.mypy.configs' 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 'thinc.tests.mypy.configs' to be distributed and are
already explicitly excluding 'thinc.tests.mypy.configs' 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)
/private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'thinc.tests.mypy.outputs' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'thinc.tests.mypy.outputs' 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 'thinc.tests.mypy.outputs' 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 'thinc.tests.mypy.outputs' to be distributed and are
already explicitly excluding 'thinc.tests.mypy.outputs' 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 thinc/__init__.pxd -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/py.typed -> build/lib.macosx-14.0-arm64-cpython-313/thinc
copying thinc/layers/premap_ids.pyx -> build/lib.macosx-14.0-arm64-cpython-313/thinc/layers
copying thinc/layers/sparselinear.pyx -> build/lib.macosx-14.0-arm64-cpython-313/thinc/layers
copying thinc/backends/__init__.pxd -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/backends/_custom_kernels.cu -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/backends/_murmur3.cu -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/backends/cblas.pxd -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/backends/cblas.pyx -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/backends/cpu_kernels.hh -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/backends/linalg.pxd -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/backends/linalg.pyx -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/backends/numpy_ops.pxd -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/backends/numpy_ops.pyx -> build/lib.macosx-14.0-arm64-cpython-313/thinc/backends
copying thinc/extra/__init__.pxd -> build/lib.macosx-14.0-arm64-cpython-313/thinc/extra
copying thinc/extra/search.pxd -> build/lib.macosx-14.0-arm64-cpython-313/thinc/extra
copying thinc/extra/search.pyx -> build/lib.macosx-14.0-arm64-cpython-313/thinc/extra
creating build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/configs
copying thinc/tests/mypy/configs/mypy-default.ini -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/configs
copying thinc/tests/mypy/configs/mypy-plugin.ini -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/configs
creating build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/outputs
copying thinc/tests/mypy/outputs/fail-no-plugin.txt -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/outputs
copying thinc/tests/mypy/outputs/fail-plugin.txt -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/outputs
copying thinc/tests/mypy/outputs/success-no-plugin.txt -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/outputs
copying thinc/tests/mypy/outputs/success-plugin.txt -> build/lib.macosx-14.0-arm64-cpython-313/thinc/tests/mypy/outputs
copying thinc/extra/tests/c_test_search.pyx -> build/lib.macosx-14.0-arm64-cpython-313/thinc/extra/tests
running build_ext
building 'thinc.backends.cblas' extension
creating build/temp.macosx-14.0-arm64-cpython-313/thinc/backends
clang++ -fno-strict-overflow -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -O3 -Wall -I/opt/homebrew/opt/zlib/include -I/private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-xhpmypa9/overlay/lib/python3.13/site-packages/numpy/_core/include -I/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13 -I/Users/local-user/Library/Caches/pypoetry/virtualenvs/eu-journal-RrXRVmn8-py3.13/include -I/opt/homebrew/opt/[email protected]/Frameworks/Python.framework/Versions/3.13/include/python3.13 -c thinc/backends/cblas.cpp -o build/temp.macosx-14.0-arm64-cpython-313/thinc/backends/cblas.o -O3 -Wno-strict-prototypes -Wno-unused-function -std=c++11
thinc/backends/cblas.cpp:871:59: warning: 'Py_UNICODE' is deprecated [-Wdeprecated-declarations]
static CYTHON_INLINE size_t __Pyx_Py_UNICODE_strlen(const Py_UNICODE *u) {
^
....
/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/cpython/longobject.h:111:17: note: candidate function not viable: requires 6 arguments, but 5 were provided
PyAPI_FUNC(int) _PyLong_AsByteArray(PyLongObject* v,
^
2 warnings and 6 errors generated.
error: command '/usr/bin/clang++' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for thinc
Building wheel for srsly (pyproject.toml): started
Building wheel for srsly (pyproject.toml): finished with status 'error'
error: subprocess-exited-with-error
× Building wheel for srsly (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [252 lines of output]
Cythonizing sources
running bdist_wheel
running build
running build_py
creating build/lib.macosx-14.0-arm64-cpython-313/srsly
copying srsly/util.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly
copying srsly/_yaml_api.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly
copying srsly/_msgpack_api.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly
copying srsly/__init__.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly
copying srsly/about.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly
copying srsly/_json_api.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly
copying srsly/_pickle_api.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly
creating build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson
copying srsly/ujson/__init__.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson
creating build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
.
.
.
.
copying srsly/tests/ruamel_yaml/test_z_data.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly/tests/ruamel_yaml
copying srsly/tests/ruamel_yaml/test_contextmanager.py -> build/lib.macosx-14.0-arm64-cpython-313/srsly/tests/ruamel_yaml
running egg_info
writing srsly.egg-info/PKG-INFO
writing dependency_links to srsly.egg-info/dependency_links.txt
writing entry points to srsly.egg-info/entry_points.txt
writing requirements to srsly.egg-info/requires.txt
writing top-level names to srsly.egg-info/top_level.txt
dependency /opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/Python.h won't be automatically included in the manifest: the path must be relative
dependency /opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/pythread.h won't be automatically included in the manifest: the path must be relative
dependency /opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/Python.h won't be automatically included in the manifest: the path must be relative
dependency /opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/pythread.h won't be automatically included in the manifest: the path must be relative
reading manifest file 'srsly.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.pxd' under directory 'srsly'
adding license file 'LICENSE'
writing manifest file 'srsly.egg-info/SOURCES.txt'
/private/var/folders/rb/_r0jpwdx5w38bzkl4vl4cqww0000gn/T/pip-build-env-4v1nh6fk/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'srsly.ujson.lib' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'srsly.ujson.lib' 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 'srsly.ujson.lib' 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 'srsly.ujson.lib' to be distributed and are
already explicitly excluding 'srsly.ujson.lib' 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 srsly/ujson/JSONtoObj.c -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson
copying srsly/ujson/objToJSON.c -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson
copying srsly/ujson/py_defines.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson
copying srsly/ujson/ujson.c -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson
copying srsly/ujson/version.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson
creating build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson/lib
copying srsly/ujson/lib/dconv_wrapper.cc -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson/lib
copying srsly/ujson/lib/ultrajson.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson/lib
copying srsly/ujson/lib/ultrajsondec.c -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson/lib
copying srsly/ujson/lib/ultrajsonenc.c -> build/lib.macosx-14.0-arm64-cpython-313/srsly/ujson/lib
copying srsly/msgpack/_packer.cpp -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/_packer.pyx -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/_unpacker.cpp -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/_unpacker.pyx -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/buff_converter.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/pack.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/pack_template.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/sysdep.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/unpack.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/unpack_define.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/msgpack/unpack_template.h -> build/lib.macosx-14.0-arm64-cpython-313/srsly/msgpack
copying srsly/tests/ujson/334-reproducer.json -> build/lib.macosx-14.0-arm64-cpython-313/srsly/tests/ujson
running build_ext
building 'srsly.msgpack._unpacker' extension
creating build/temp.macosx-14.0-arm64-cpython-313/srsly/msgpack
clang++ -fno-strict-overflow -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -O3 -Wall -I/opt/homebrew/opt/zlib/include -D__LITTLE_ENDIAN__=1 -Isrsly/msgpack -I/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13 -I. -I/Users/local-user/Library/Caches/pypoetry/virtualenvs/eu-journal-RrXRVmn8-py3.13/include -I/opt/homebrew/opt/[email protected]/Frameworks/Python.framework/Versions/3.13/include/python3.13 -c srsly/msgpack/_unpacker.cpp -o build/temp.macosx-14.0-arm64-cpython-313/srsly/msgpack/_unpacker.o -O2 -Wno-strict-prototypes -Wno-unused-function
srsly/msgpack/_unpacker.cpp:877:59: warning: 'Py_UNICODE' is deprecated [-Wdeprecated-declarations]
static CYTHON_INLINE size_t __Pyx_Py_UNICODE_strlen(const Py_UNICODE *u) {
^
/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/cpython/unicodeobject.h:10:1: note: 'Py_UNICODE' has been explicitly marked deprecated here
Py_DEPRECATED(3.13) typedef wchar_t Py_UNICODE;
^
/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/pyport.h:251:54: note: expanded from macro 'Py_DEPRECATED'
#define Py_DEPRECATED(VERSION_UNUSED) __attribute__((__deprecated__))
^
srsly/msgpack/_unpacker.cpp:878:11: warning: 'Py_UNICODE' is deprecated [-Wdeprecated-declarations]
const Py_UNICODE *u_end = u;
^
/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/cpython/unicodeobject.h:10:1: note: 'Py_UNICODE' has been explicitly marked deprecated here
Py_DEPRECATED(3.13) typedef wchar_t Py_UNICODE;
^
/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/pyport.h:251:54: note: expanded from macro 'Py_DEPRECATED'
#define Py_DEPRECATED(VERSION_UNUSED) __attribute__((__deprecated__))
^
srsly/msgpack/_unpacker.cpp:2605:17: error: use of undeclared identifier 'PyObject_AsReadBuffer'; did you mean 'PyObject_GetBuffer'?
__pyx_t_2 = PyObject_AsReadBuffer(__pyx_v_obj, ((void const **)__pyx_v_buf), __pyx_v_buffer_len); if (unlikely(__pyx_t_2 == ((int)-1))) __PYX_ERR(0, 136, __pyx_L1_error)
^~~~~~~~~~~~~~~~~~~~~
PyObject_GetBuffer
/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/pybuffer.h:46:17: note: 'PyObject_GetBuffer' declared here
PyAPI_FUNC(int) PyObject_GetBuffer(PyObject *obj, Py_buffer *view,
^
srsly/msgpack/_unpacker.cpp:2605:52: error: cannot initialize a parameter of type 'Py_buffer *' with an rvalue of type 'const void **'
__pyx_t_2 = PyObject_AsReadBuffer(__pyx_v_obj, ((void const **)__pyx_v_buf), __pyx_v_buffer_len); if (unlikely(__pyx_t_2 == ((int)-1))) __PYX_ERR(0, 136, __pyx_L1_error)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/pybuffer.h:46:62: note: passing argument to parameter 'view' here
PyAPI_FUNC(int) PyObject_GetBuffer(PyObject *obj, Py_buffer *view,
^
srsly/msgpack/_unpacker.cpp:9638:27: error: no matching function for call to '_PyLong_AsByteArray'
int ret = _PyLong_AsByteArray((PyLongObject *)v,
^~~~~~~~~~~~~~~~~~~
/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/cpython/longobject.h:111:17: note: candidate function not viable: requires 6 arguments, but 5 were provided
PyAPI_FUNC(int) _PyLong_AsByteArray(PyLongObject* v,
^
srsly/msgpack/_unpacker.cpp:9834:27: error: no matching function for call to '_PyLong_AsByteArray'
int ret = _PyLong_AsByteArray((PyLongObject *)v,
^~~~~~~~~~~~~~~~~~~
/opt/homebrew/Cellar/[email protected]/3.13.0_1/Frameworks/Python.framework/Versions/3.13/include/python3.13/cpython/longobject.h:111:17: note: candidate function not viable: requires 6 arguments, but 5 were provided
PyAPI_FUNC(int) _PyLong_AsByteArray(PyLongObject* v,
^
2 warnings and 4 errors generated.
error: command '/usr/bin/clang++' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for srsly
Failed to build thinc srsly
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (thinc, srsly)
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: pip install --upgrade pip
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.