issue_comments: 872009559

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/5545#issuecomment-872009559 https://api.github.com/repos/pydata/xarray/issues/5545 872009559 MDEyOklzc3VlQ29tbWVudDg3MjAwOTU1OQ== 4160723 2021-07-01T07:47:51Z 2021-07-01T07:47:51Z MEMBER

My 2 cents (no strong view either, I'm mostly using the HTML repr with a rather small number of variables):

I do agree with both arguments "fit the screen" vs "need to see all the variables", so why not have different display rules for the Dataset, Dataset.data_vars and Dataset.coords reprs?

For the Dataset repr, I think the motivation is mostly to get a quick overview of the whole dataset and basic answers on questions like:

  • What are the dimensions and their size?
  • How many coordinates and data variables?
  • Is the dataset fully loaded in memory or lazily loaded? Are the variables chunked? What's the type of arrays (dask vs. numpy)?
  • Is there a lot of metadata or no metadata at all (global attributes)?

All those questions can be answered with a short, truncated repr.

For the Dataset.data_vars and Dataset.coords reprs, it's more obvious that we want to see all of them, so I'd suggest not limiting the maximum of rows displayed (or have a much larger limit? but then we duplicate the display options, which is not very nice).

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   931591247