home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 869763953

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-869763953 https://api.github.com/repos/pydata/xarray/issues/5545 869763953 MDEyOklzc3VlQ29tbWVudDg2OTc2Mzk1Mw== 14808389 2021-06-28T15:06:23Z 2021-06-28T15:06:23Z MEMBER

choosing default values is hard and always some kind of a tradeoff. In general we should strive to choose a default that is useful to most users (but how do you measure "useful to most users"?), and if that is not the case for a particular use case it should be configurable. I agree that having to remember to add the set_options call in every script / notebook / interpreter session is annoying, but there is not too much we can do (except adding a configuration file? but that might make the set_options code more complicated...)

For this particular setting I think the idea for the current value was that printing a lot of variables is slow and, most importantly, that the repr should provide an overview of the object, and in my opinion not being able to have all sections visible reduces the usefulness of the repr (which is why I tend to also set display_expand_data=False at the top of my notebooks). In the PR that introduced the setting we somewhat arbitrarily chose the number 12 but I don't think it should be much higher.

Thoughts, @pydata/xarray?

Disabling the restriction should be possible (but again, not the default), maybe xr.set_options(display_max_rows=float("inf")) works?

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  931591247
Powered by Datasette · Queries took 0.686ms · About: xarray-datasette