DOC: Update array API docs after changes in logic and design#3125
Merged
david-cortes-intel merged 1 commit intoMay 19, 2026
Merged
Conversation
yuejiaointel
approved these changes
May 19, 2026
234d7da
into
uxlfoundation:main
15 of 16 checks passed
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
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.
Description
There have been several changes in how array API support works in scikit-learn and fixes in sklearnex that now make some statements in the documentation obsolete.
For example, by now all public-facing attributes of array API estimators should be of array API classes, which was not the case before, and implementation of 'everything follows X' logic is in progress, so now more potential input combinations are allowed.
The documentation will need further updates after implementing
move_to.Checklist:
Completeness and readability
Testing