You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider using a Rich table maybe? It is "bigger" but looks more professional. See below for argument against this.
Generally, color might be nice.
The dependencies must be formatted more nicely. One dependency per row to more easily digest the information
Argument against Rich tables: They cannot be properly collapsed. Consider using HTML formatting to allow for the interactive selection and hiding of information.
The text was updated successfully, but these errors were encountered:
Thanks, Lukas! This is valuable feedback! We'll consider, and I'd also really like to discuss.
Rationale for dependency formatting is having them copy-pastable into a pip install .... If we do it in any other way, that won't be the case anymore. They're alphabetically sorted, and they're not meant to explode but represent the key dependencies the analyst deems crucial for the result of the notebook.
I have a quite strong opinion of keeping them in one row until things get fancier an interactive. But I'm also happy to re-think that opinion!
From the docs
50% of the success is visuals :)
The text was updated successfully, but these errors were encountered: