Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing sklearn instead of scikit-learn #8

Open
D1midr0sh opened this issue Apr 16, 2024 · 0 comments
Open

Installing sklearn instead of scikit-learn #8

D1midr0sh opened this issue Apr 16, 2024 · 0 comments

Comments

@D1midr0sh
Copy link

When installing ExploriPy I get a following error:

Collecting sklearn (from ExploriPy==1.1.2)
 Using cached sklearn-0.0.post12.tar.gz (2.6 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 'error'
Note: you may need to restart the kernel to use updated packages.
 error: subprocess-exited-with-error
 
 × Getting requirements to build wheel did not run successfully.
 │ exit code: 1
 ╰─> [15 lines of output]
     The 'sklearn' PyPI package is deprecated, use 'scikit-learn'
     rather than 'sklearn' for pip commands.
     
     Here is how to fix this error in the main use cases:
     - use 'pip install scikit-learn' rather than 'pip install sklearn'
     - replace 'sklearn' by 'scikit-learn' in your pip requirements files
       (requirements.txt, setup.py, setup.cfg, Pipfile, etc ...)
     - if the 'sklearn' package is used by one of your dependencies,
       it would be great if you take some time to track which package uses
       'sklearn' instead of 'scikit-learn' and report it to their issue tracker
     - as a last resort, set the environment variable
       SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL=True to avoid this error
     
     More information is available at
     https://github.com/scikit-learn/sklearn-pypi-package
     [end of output]
 
 note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

It seems that installer tries to use deprecated "sklearn"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant