home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where issue = 677307460 and user = 6063709 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • aidanheerdegen · 2 ✖

issue 1

  • cftime_range does not support default cftime.datetime formatted output strings · 2 ✖

author_association 1

  • CONTRIBUTOR 2
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
673840314 https://github.com/pydata/xarray/issues/4337#issuecomment-673840314 https://api.github.com/repos/pydata/xarray/issues/4337 MDEyOklzc3VlQ29tbWVudDY3Mzg0MDMxNA== aidanheerdegen 6063709 2020-08-14T01:56:49Z 2020-08-14T01:56:49Z CONTRIBUTOR

Turns zero-padding years is platform dependent.

https://bugs.python.org/issue13305

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  cftime_range does not support default cftime.datetime formatted output strings 677307460
673769082 https://github.com/pydata/xarray/issues/4337#issuecomment-673769082 https://api.github.com/repos/pydata/xarray/issues/4337 MDEyOklzc3VlQ29tbWVudDY3Mzc2OTA4Mg== aidanheerdegen 6063709 2020-08-14T00:08:22Z 2020-08-14T00:08:22Z CONTRIBUTOR

Thanks for the detailed response @spencerkclark

Seems that we're using different versions of python as my datetime implementation doesn't produce a zero padded year. I guess that was a bug that has also been fixed: ```python In [1]: import datetime

In [2]: datetime.datetime(1, 1, 1).strftime("%Y-%m-%dT%H:%M:%S") Out[2]: '1-01-01T00:00:00' `` I agree that theisoformatis a good solution. I didn't know it was available in newer versions. I will upgrade mycftimeversion to>=1.1.3` to access it.

Thanks for being open to supporting the default output. My only goal is to remove barriers to productivity and remove sources of confusion as I want these tools to be used, and embraced, as widely as possible.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  cftime_range does not support default cftime.datetime formatted output strings 677307460

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]);
Powered by Datasette · Queries took 15.082ms · About: xarray-datasette