fix: ensure scikit-learn package name consistency in library imports #681
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix: Correct scikit-learn package name in dependency installation
Problem
When users try to import
sklearn
in their evaluation scripts, they might get confused about the correct package name for installation.Solution
Added logic to ensure users are directed to install the correct package name
scikit-learn
instead ofsklearn
when dependencies are missing.#Previous Import error message:
ImportError: To be able to use evaluate-metric/accuracy, you need to install the following dependencies['scikit-learn'] using 'pip install sklearn' for instance'
#Correct Import error message:
ImportError: To be able to use evaluate-metric/accuracy, you need to install the following dependencies['scikit-learn'] using 'pip install scikit-learn' for instance'
Changes
Impact
Users will now receive the correct installation command (
pip install scikit-learn
) instead of the incorrect one (pip install sklearn
) when the package is not installed, preventing confusion and ensuring successful package installation.