[MNT] set_params

[arnavk23]

Reference Issues/PRs

Fixes #469

What does this implement/fix? Explain your changes.

Calling set_params() with no keyword arguments will reset the object to post-init state (consistent contract: any call to set_params mutates state). This makes behaviour consistent across BaseObject and meta-objects. We want calls to set_params() (even with no kwargs) to reset the object, keeping the contract that set_params mutates state. Previously this early-return prevented meta-objects from resetting when invoked with no params.

Does your contribution introduce a new dependency? If yes, which one?

What should a reviewer concentrate their feedback on?

Any other comments?

@arnavk23 ➜ /workspaces/skbase (main) $ PYTEST_ADDOPTS="" python -m pytest -c /dev/null -q
.............................................................. [  3%]
.............................................................. [  7%]
.............................................................. [ 11%]
.............................................................. [ 15%]
.............................................................. [ 19%]
.............................................................. [ 23%]
.............................................................. [ 27%]
.............................................................. [ 31%]
.............................................................. [ 35%]
.............................................................. [ 39%]
.............................................................. [ 43%]
.............................................................. [ 47%]
.............................................................. [ 51%]
.............................................................. [ 55%]
.............................................................. [ 59%]
.............................................................. [ 63%]
.............................................................. [ 67%]
.............................................................. [ 70%]
.............................................................. [ 74%]
.............................................................. [ 78%]
.............................................................. [ 82%]
.............................................................. [ 86%]
.............................................................. [ 90%]
.............................................................. [ 94%]
.............................................................. [ 98%]
......................                                         [100%]
========================== warnings summary ==========================
skbase/tests/test_base.py::test_clone_none_and_empty_array_nan_sparse_matrix[c_value2]
  /home/codespace/.local/lib/python3.12/site-packages/numpy/testing/_private/utils.py:857: SparseEfficiencyWarning: Comparing two sparse matrices using == is inefficient. Try using != instead.
    val = comparison(x, y)

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1448: FutureWarning: tag 'old_tag_1' will be removed in version 42.0.0 and replaced by 'new_tag_1', please use 'new_tag_1' instead
    self._deprecate_tag_warn([tag_name])

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1320: FutureWarning: tag 'old_tag_1' will be removed in version 42.0.0 and replaced by 'new_tag_1', please use 'new_tag_1' instead
    cls._deprecate_tag_warn([tag_name])

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1448: FutureWarning: tag 'old_tag_2' will be removed in version 84.0.0 and replaced by 'new_tag_2', please use 'new_tag_2' instead
    self._deprecate_tag_warn([tag_name])

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1320: FutureWarning: tag 'old_tag_2' will be removed in version 84.0.0 and replaced by 'new_tag_2', please use 'new_tag_2' instead
    cls._deprecate_tag_warn([tag_name])

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1448: FutureWarning: tag 'old_tag_3' will be removed in version 126.0.0 and replaced by 'new_tag_3', please use 'new_tag_3' instead
    self._deprecate_tag_warn([tag_name])

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1320: FutureWarning: tag 'old_tag_3' will be removed in version 126.0.0 and replaced by 'new_tag_3', please use 'new_tag_3' instead
    cls._deprecate_tag_warn([tag_name])

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1400: FutureWarning: tag 'old_tag_1' will be removed in version 42.0.0 and replaced by 'new_tag_1', please use 'new_tag_1' instead
    self._deprecate_tag_warn(collected_tags)

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1400: FutureWarning: tag 'old_tag_3' will be removed in version 126.0.0 and replaced by 'new_tag_3', please use 'new_tag_3' instead
    self._deprecate_tag_warn(collected_tags)

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1277: FutureWarning: tag 'old_tag_1' will be removed in version 42.0.0 and replaced by 'new_tag_1', please use 'new_tag_1' instead
    cls._deprecate_tag_warn(collected_tags)

skbase/tests/test_tagaliaser.py::test_tag_aliaser
  /workspaces/skbase/skbase/base/_base.py:1277: FutureWarning: tag 'old_tag_3' will be removed in version 126.0.0 and replaced by 'new_tag_3', please use 'new_tag_3' instead
    cls._deprecate_tag_warn(collected_tags)

../../usr/local/python/3.12.1/lib/python3.12/site-packages/_pytest/cacheprovider.py:475
  /usr/local/python/3.12.1/lib/python3.12/site-packages/_pytest/cacheprovider.py:475: PytestCacheWarning: could not create cache path /dev/.pytest_cache/v/cache/nodeids: [Errno 13] Permission denied: '/dev/pytest-cache-files-3sxpdm2s'
    config.cache.set("cache/nodeids", sorted(self.cached_nodeids))

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
1572 passed, 12 warnings in 22.31s

PR checklist

For all contributions

• I've reviewed the project documentation on contributing
• I've added myself to the list of contributors.
• The PR title starts with either [ENH], [CI/CD], [MNT], [DOC], or [BUG] indicating whether
  the PR topic is related to enhancement, CI/CD, maintenance, documentation, or a bug.

For code contributions

• Unit tests have been added covering code functionality
• Appropriate docstrings have been added (see documentation standards)
• New public functionality has been added to the API Reference

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.32%. Comparing base (306958d) to head (36b4278).
⚠️ Report is 177 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #472      +/-   ##
==========================================
- Coverage   85.07%   83.32%   -1.75%     
==========================================
  Files          45       52       +7     
  Lines        3015     3880     +865     
==========================================
+ Hits         2565     3233     +668     
- Misses        450      647     +197     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.