Damien

Well dang, it appears this deprecation just came through with 1.5. Do we have a link to the relevant discussion? I wonder if it is going back to sklearn.utils.testing as...

Then let's shelve it until sklearn 1.7 to see what alternative they'll use (the function is quite useful, I doubt they'll remove it entirely unless of course it's too much...

relevant documentation sklearn-side: [https://scikit-learn.org/stable/auto_examples/miscellaneous/plot_metadata_routing.html#third-party-development-and-scikit-learn-dependency](https://scikit-learn.org/stable/auto_examples/miscellaneous/plot_metadata_routing.html#third-party-development-and-scikit-learn-dependency)

Checked the PR, and it does mention metadata routing wit the set_fit_request flag, but it was bumped in another PR an example of a very simple thing which is not...

I don't think _MetadataRequester is needed: class _MetadataRequester: """Mixin class for adding metadata request functionality. ---> ``BaseEstimator`` inherits from this Mixin. .. versionadded:: 1.3 """ A skorch specific part would...

Been playing with this for a bit too. The main problem here is the ability to use torch_geometric with complex pipelines, which often await tabular data. proposed solution: metadata routing....