Riccardo Cappuzzo
Riccardo Cappuzzo
Hey @georgescutelnicu, I overlooked a different solution that would simplify this PR a lot, and would make it more convenient to set up. A recent PR implemented a global config...
Closing this in favor of #1470
This issue can be fixed by editing the file `doc/table_report.py`, doing something like ```python X = X.sample(frac=1, random_state=11) ``` with a specific `random_state` to ensure reproducibility.
An object like this would be very useful to trim tables before running the TableReport on them #1257
> I wonder if such functionality should be in the TableReport, or rather in the column_association function, but not exposed in the TableReport. It seems a bit specific and low...
Given that the TableReport has the `order_by` parameter to specify a column to order by, maybe we can piggyback off that and report only the associations that are relative to...
Discussing with @glemaitre, we could split the note so that at the top there is only a short mention like "such and such is a column transformer, so it works...
> Discussing with ***@***.***, we could split the note so that at the top there is only a short mention like "such and such is a column transformer, so it...
From IRL discussion: Good to have, but should not be a blocker for 0.6.0. We can release a fix in 0.6.1
The text that is used in the note is defined in `_apply_to_cols.py` in `_SINGLE_COL_LINE`. This string should be modified and summarized so that the start of the docstring only contains...