When I try to install spaCy to use with chatterBot (somehow it didn’t download with ChatterBot), first I got an error because I did not have the Cython module installed into my virtual environment, and then I got stuck into this:
pip install spacy
Collecting spacy
Using cached spacy-3.7.5-cp38-cp38-win_amd64.whl.metadata (27 kB)
Collecting spacy-legacy<3.1.0,>=3.0.11 (from spacy)
Using cached spacy_legacy-3.0.12-py2.py3-none-any.whl.metadata (2.8 kB)
...
Building wheels for collected packages: thinc
Building wheel for thinc (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for thinc (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [448 lines of output]
Cythonizing sources
running bdist_wheel
running build
running build_py
creating build
creating buildlib.win-amd64-cpython-38
creating buildlib.win-amd64-cpython-38thinc
... copying and creating stuff ...
dependency C:UsersscrhtAppDataLocalProgramsPythonPython38IncludePython.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyarrayobject.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyarrayscalars.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyndarrayobject.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyndarraytypes.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyufuncobject.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalProgramsPythonPython38IncludePython.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyarrayobject.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyarrayscalars.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyndarrayobject.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyndarraytypes.h won't be automatically included in the manifest: the path must be relative
dependency C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagesnumpycoreincludenumpyufuncobject.h won't be automatically included in the manifest: the path must be relative
reading manifest file 'thinc.egg-infoSOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: manifest_maker: MANIFEST.in, line 4: path 'tmp/' cannot end with '/'
warning: no previously-included files matching '*.cpp' found under directory 'thinc'
adding license file 'LICENSE'
writing manifest file 'thinc.egg-infoSOURCES.txt'
C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagessetuptoolscommandbuild_py.py:215: _Warning: Package 'thinc.backends' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'thinc.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 'thinc.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 'thinc.backends' to be distributed and are
already explicitly excluding 'thinc.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)
C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagessetuptoolscommandbuild_py.py:215: _Warning: Package 'thinc.extra' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'thinc.extra' 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.extra' 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.extra' to be distributed and are
already explicitly excluding 'thinc.extra' 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)
C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagessetuptoolscommandbuild_py.py:215: _Warning: Package 'thinc.layers' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'thinc.layers' 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.layers' 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.layers' to be distributed and are
already explicitly excluding 'thinc.layers' 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)
C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagessetuptoolscommandbuild_py.py:215: _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)
copying thinc__init__.pxd -> buildlib.win-amd64-cpython-38thinc
copying thincpy.typed -> buildlib.win-amd64-cpython-38thinc
copying thincbackendscblas.cpp -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackendscpu_kernels.hh -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackendslinalg.cpp -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackendsnumpy_ops.cpp -> buildlib.win-amd64-cpython-38thincbackends
copying thincextrasearch.cpp -> buildlib.win-amd64-cpython-38thincextra
copying thinclayerspremap_ids.cpp -> buildlib.win-amd64-cpython-38thinclayers
copying thinclayerssparselinear.cpp -> buildlib.win-amd64-cpython-38thinclayers
copying thincbackends__init__.pxd -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackends_custom_kernels.cu -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackends_murmur3.cu -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackendscblas.pxd -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackendscblas.pyx -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackendslinalg.pxd -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackendslinalg.pyx -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackendsnumpy_ops.pxd -> buildlib.win-amd64-cpython-38thincbackends
copying thincbackendsnumpy_ops.pyx -> buildlib.win-amd64-cpython-38thincbackends
copying thincextra__init__.pxd -> buildlib.win-amd64-cpython-38thincextra
copying thincextrasearch.pxd -> buildlib.win-amd64-cpython-38thincextra
copying thincextrasearch.pyx -> buildlib.win-amd64-cpython-38thincextra
copying thinclayerspremap_ids.pyx -> buildlib.win-amd64-cpython-38thinclayers
copying thinclayerssparselinear.pyx -> buildlib.win-amd64-cpython-38thinclayers
copying thincextratestsc_test_search.pyx -> buildlib.win-amd64-cpython-38thincextratests
creating buildlib.win-amd64-cpython-38thinctestsmypyconfigs
copying thinctestsmypyconfigsmypy-default.ini -> buildlib.win-amd64-cpython-38thinctestsmypyconfigs
copying thinctestsmypyconfigsmypy-plugin.ini -> buildlib.win-amd64-cpython-38thinctestsmypyconfigs
creating buildlib.win-amd64-cpython-38thinctestsmypyoutputs
copying thinctestsmypyoutputsfail-no-plugin.txt -> buildlib.win-amd64-cpython-38thinctestsmypyoutputs
copying thinctestsmypyoutputsfail-plugin.txt -> buildlib.win-amd64-cpython-38thinctestsmypyoutputs
copying thinctestsmypyoutputssuccess-no-plugin.txt -> buildlib.win-amd64-cpython-38thinctestsmypyoutputs
copying thinctestsmypyoutputssuccess-plugin.txt -> buildlib.win-amd64-cpython-38thinctestsmypyoutputs
running build_ext
C:UsersscrhtAppDataLocalTemppip-build-env-_hk7kebroverlayLibsite-packagessetuptoolscommandbuild_py.py:215: _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)
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for thinc
Failed to build thinc
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (thinc)
python 3.8.0 and pip 24.1.2
I tried to install some old versions of spaCy, but it didn’t help me (the problem appears again). I’m trying to install Virtual Studio Tools.
1