issue_comments

Table actions

5 rows where issue = 89866276 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 2

issue 1

  • Display datetime64 arrays without showing local timezones · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
212979439 https://github.com/pydata/xarray/issues/439#issuecomment-212979439 https://api.github.com/repos/pydata/xarray/issues/439 MDEyOklzc3VlQ29tbWVudDIxMjk3OTQzOQ== shoyer 1217238 2016-04-21T15:43:27Z 2016-04-21T15:43:27Z MEMBER

The good news is that I fixed this display bug upstream in NumPy 1.11, which came out last month. If you upgrade to NumPy 1.11, datetimes are always treated as timezone naive. So I think we can actually consider this issue fixed.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Display datetime64 arrays without showing local timezones 89866276
212942750 https://github.com/pydata/xarray/issues/439#issuecomment-212942750 https://api.github.com/repos/pydata/xarray/issues/439 MDEyOklzc3VlQ29tbWVudDIxMjk0Mjc1MA== andreas-h 358378 2016-04-21T14:28:32Z 2016-04-21T14:28:32Z CONTRIBUTOR

sounds good to me, @sjpfenninger, but I don't know the internals ...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Display datetime64 arrays without showing local timezones 89866276
212940728 https://github.com/pydata/xarray/issues/439#issuecomment-212940728 https://api.github.com/repos/pydata/xarray/issues/439 MDEyOklzc3VlQ29tbWVudDIxMjk0MDcyOA== sjpfenninger 141709 2016-04-21T14:23:54Z 2016-04-21T14:23:54Z CONTRIBUTOR

Would it not make sense to use a pandas.DatetimeIndex instead of pure-numpy datetimes? It seems that DatetimeIndex already solves lots of the weirdness in the underlying numpy datetime objects and adds a bunch of useful functionality for things like groupby operations.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Display datetime64 arrays without showing local timezones 89866276
124657664 https://github.com/pydata/xarray/issues/439#issuecomment-124657664 https://api.github.com/repos/pydata/xarray/issues/439 MDEyOklzc3VlQ29tbWVudDEyNDY1NzY2NA== shoyer 1217238 2015-07-24T19:29:03Z 2015-07-24T19:29:03Z MEMBER

https://github.com/xray/xray/blob/v0.5.2/xray/core/formatting.py#L250

The repr call on this line would need to be replaced with another function that checks the dtype of the numpy array and uses custom handling for datetime64.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Display datetime64 arrays without showing local timezones 89866276
124637042 https://github.com/pydata/xarray/issues/439#issuecomment-124637042 https://api.github.com/repos/pydata/xarray/issues/439 MDEyOklzc3VlQ29tbWVudDEyNDYzNzA0Mg== andreas-h 358378 2015-07-24T19:04:09Z 2015-07-24T19:04:09Z CONTRIBUTOR

can you give a pointer to where this would need to be done in the code?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Display datetime64 arrays without showing local timezones 89866276

Advanced export

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

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);