✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

_{Generated for commit: d4691ff. Link to the linter CI: here}

Please not so fast. Have we decided this in a closed call without open discussion?

I know the release is approaching, but it feels rushed.

@StefanieSenger the open discussion is here: #29048 (comment)

@StefanieSenger the open discussion is here: #29048 (comment)

This is a summary of a closed discussion.

We didn't decide in a call to revert these changes. As a result of the discussion written in that issue, it became clear that we should revert these changes to avoid having to immediately deprecate something that we are going to release. So it makes sense to revert, so that we then put the new design in, w/o making the users go through a deprecation cycle.

So it makes sense to revert, so that we then put the new design in, w/o making the users go through a deprecation cycle.

Yes it makes sense if we follow the path discussed in the private call. I can see it helps users not to go through a deprecation cycle and it might be the right decision overall.

What I mean is that you don't give others the chance to voice their opinion.

The comments on the issue and this PR is the place for people to give their opinions. However, there are enough people who don't want this to be released as it is right now, that it doesn't matter what others think. In scikit-learn, when we have some maintainers who are negative on a change, we have to find a better solution. That takes time and people are given time to raise their concerns. However, this is about preventing to push out a change in a release that some of us are not happy with. Therefore it needs to be pulled out of the release, and that doesn't need much of a discussion.

However, how to replace it and how to move forward with it, needs discussion and very happy to have everyone's opinion about that.

Therefore it needs to be pulled out of the release, and that doesn't need much of a discussion.

However, how to replace it and how to move forward with it, needs discussion and very happy to have everyone's opinion about that.

Okay, I can see your perspective on that and I agree that it is objectively the best way to do this.

I solved the merge conflict.