issues

Table actions

1 row where repo = 13221727, type = "issue" and user = 9097307 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date), closed_at (date)

type 1

  • issue · 1 ✖

state 1

repo 1

  • xarray · 1 ✖
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
124129804 MDU6SXNzdWUxMjQxMjk4MDQ= 687 Dataset.T property creates conflict with data named 'T' brian-rose 9097307 closed 0     3 2015-12-28T21:30:58Z 2015-12-29T03:09:47Z 2015-12-29T03:09:47Z CONTRIBUTOR      

I frequently find myself working with datasets that include a variable named 'T' (for temperature!)

The problem with this is that, unlike any other variable, mydataset.T does not return the variable, because there is a built-in property .T which is just a map to the mydataset.transpose() method.

This is mostly just a minor annoyance, because of course I can access the data as mydataset['T'], but it necessitates an odd asymmetry in any code that accesses T as well as other data. And, maybe more importantly, mydataset.T does NOT immediately raise an error in code that is attempting to access the temperature data.

I have not been able to simply remove the property interactively from the dataset objects, e.g. del mydataset.T raises an error AttributeError: can't delete attribute

Since the transpose functionality is already easily accessible through mydataset.transpose() (which is more readable, in my opinion), perhaps the T property should just be removed?

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

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);