Francesco Bruzzesi

Added high prio label as it was requested in discord as well - I think it is both in scope and doable (must double check performance though 🙈)

@MarcoGorelli since #2998 would bring us half way through this issue, I wonder how `is_elementwise` would look like for pandas-like and pyarrow. Or would we let it exist just for...

Thanks for the contribution @AhmedThahir 🚀 > @FBruzzesi, this is the best I could do, have not been able to understand how to proceed. If you could take some time...

Hey @AhmedThahir thanks for pushing the changes > Still failing these tests when I run `pytest tests/test_meta/test_hierarchical_predictor.py` I am trying to debug the tests locally. From what I can see:...

> Any action required from my side ? Hey @AhmedThahir, not really! If you are interested you can think about how we can test most of the hierchical functionalities and...

> I'm not sure if I'm quite sure how to proceed here. the inbuilt check sample weights seems to take care of all cases that I can think of. Hey...

Hey @AhmedThahir , that's definitly a reasonable request. We have such option for `OrdinalClassifier`. Concern is only about the fact that majority of estimators also allow to fit in parallel,...

Hey @AhmedThahir , it turns out that I completely forgot that we already support such feature in [HierarchicalClassifier](https://koaning.github.io/scikit-lego/api/meta/#sklego.meta.hierarchical_predictor.HierarchicalClassifier) and [HierarchicalRegressor](https://koaning.github.io/scikit-lego/api/meta/#sklego.meta.hierarchical_predictor.HierarchicalRegressor), which in general have a better design compared to Grouped...

You can fit the lowest level only by specifying `fallback_method="raise", shrinkage=None`. From the docs: > [...] This means that an estimator is fitted for each level of the group columns....

1. I don't think it is possible to do so in Hierarchical at the moment, but it could be in scope for the `shrinkage=None` case. 2. Quoting a [comment](https://github.com/koaning/scikit-lego/issues/616#issuecomment-1968630402) directly:...