home / github / issues

Menu
  • Search all tables
  • GraphQL API

issues: 197920258

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
197920258 MDU6SXNzdWUxOTc5MjAyNTg= 1188 Should we deprecate the compat and encoding constructor arguments? 2443309 closed 0     5 2016-12-28T21:41:26Z 2020-03-24T14:34:37Z 2020-03-24T14:34:37Z MEMBER      

In https://github.com/pydata/xarray/pull/1170#discussion_r94078121, @shoyer writes:

...I would consider deprecating the encoding argument to DataArray instead. It would also make sense to get rid of the compat argument to Dataset.

These extra arguments are not part of the fundamental xarray data model and thus are a little distracting, especially to new users.

@pydata/xarray and others, what do we think about deprecating the compat argument to the Dataset constructor and the encoding arguement to the DataArray (and Dataset via #1170).

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1188/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed 13221727 issue

Links from other tables

  • 0 rows from issues_id in issues_labels
  • 5 rows from issue in issue_comments
Powered by Datasette · Queries took 239.906ms · About: xarray-datasette