fix: compare joblib versions semantically#2242
Open
he-yufeng wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
joblib.__version__withpackaging.version.parse()instead of raw strings1.10.0joblib version stringWhy
ParallelExtselects between joblib's old_backend_argsand newer_backend_kwargsattributes based on the joblib version. A raw string comparison treats"1.10.0"as lower than"1.5.0", which would send newer joblib releases down the removed_backend_argspath.Tests
python -m py_compile qlib\\utils\\paral.py tests\\misc\\test_paral.pypython -m pytest tests\\misc\\test_paral.py -qgit diff --check