Skip to content

requirement is not satisfied error (python 3.9.6) #2

Description

@peyamekenel

(venv) PS C:\Users\xx\tagBase\Revisiting-the-Tag-Relevance-Prediction-Problem> pip install -r requirements.txt
Collecting sparsesvd==0.2.2 (from -r requirements.txt (line 1))
Using cached sparsesvd-0.2.2.tar.gz (36 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [29 lines of output]
C:\Users\xx\AppData\Local\Temp\pip-build-env-zgopnuth\overlay\Lib\site-packages\setuptools_distutils\dist.py:289: UserWarning: Unknown distribution option: 'test_suite'
warnings.warn(msg)
C:\Users\xx\AppData\Local\Temp\pip-build-env-zgopnuth\overlay\Lib\site-packages\setuptools\dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

          ********************************************************************************
          Please consider removing the following classifiers in favor of a SPDX license expression:
 
          License :: OSI Approved :: BSD License
 
          See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
          ********************************************************************************
 
  !!
    self._finalize_license_expression()
  error: Multiple top-level packages discovered in a flat-layout: ['Pyrex', 'SVDLIBC'].
 
  To avoid accidental inclusion of unwanted files or directories,
  setuptools will not proceed with this build.
 
  If you are trying to create a single distribution with multiple packages
  on purpose, you should not rely on automatic discovery.
  Instead, consider the following options:
 
  1. set up custom discovery (`find` directive with `include` or `exclude`)
  2. use a `src-layout`
  3. explicitly set `py_modules` or `packages` with a list of names
 
  To find more information, look for "package discovery" on setuptools docs.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions