fix flake8 errors due to new pypi dependency/rule updates #597
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 new flake8 errors that started to appear in gated builds after new versions of flake8 helper packages were released with new rules.
Specifically, I believe these are from flake8-bugbear and flake8-pytest-style updates.
Also temporarily pin scikit-learn<=1.4.2 due to issue with econml and scikit-learn in tests when validating ExplanationDashboard visualization from raiwidgets package.
Copilot summary:
This pull request primarily involves syntax modifications across several Python test files. The most significant changes include the addition of a specific error code to a
BaseException
ingpu_kmeans.py
, and the removal of parentheses from several pytest decorators inconftest.py
andtest_notebooks.py
.Here are the key changes:
Syntax modifications:
python/interpret_community/common/gpu_kmeans.py
: Added a specific error code to theBaseException
to adhere to linting rules.tests/conftest.py
: Removed parentheses from thepytest.fixture
decorator, which is a more Pythonic style.tests/test_notebooks.py
: Removed parentheses from thepytest.mark.notebooks
decorator in multiple test methods. This change was made consistently across several methods to maintain a uniform coding style. [1] [2] [3] [4] [5] [6] [7]