issue_comments

Table actions

2 rows where issue = 961780560 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • Do not require on pkg_resources as it drastically increases import time. · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
893467249 https://github.com/pydata/xarray/issues/5676#issuecomment-893467249 https://api.github.com/repos/pydata/xarray/issues/5676 IC_kwDOAMm_X841QTpx keewis 14808389 2021-08-05T13:38:02Z 2021-08-05T13:38:02Z MEMBER

we had a lengthy discussion about a related topic in #4295. Long story short: we will be able to switch to importlib.metadata once we can drop support for py37 (and we can already use importlib.resources for the CSS and HTML files, feel free to send in a PR for that).

For the backends, we could use the separate entrypoints library (which I believe is faster), but as far as I can tell we will only make that switch once we can drop the dependency on pkg_resources entirely.

For reference, NEP29 allows dropping support for py37 after Dec 26.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Do not require on pkg_resources as it drastically increases import time. 961780560
893459440 https://github.com/pydata/xarray/issues/5676#issuecomment-893459440 https://api.github.com/repos/pydata/xarray/issues/5676 IC_kwDOAMm_X841QRvw benbovy 4160723 2021-08-05T13:27:09Z 2021-08-05T13:29:11Z MEMBER

There are better approaches to set the version number than to use this heavy weight module. For instance setuptools_scm.

Looks like it is still required to retrieve the version number at runtime for python versions < 3.8, unless we agree to temporarily depend on the importlib_metada backport.

As far as I could see, the module is used to set the version number of xarray

It is also used for the backend entry-points and for loading a couple of static css/html files for the html reprs. I don't know if there are better approaches for this, though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Do not require on pkg_resources as it drastically increases import time. 961780560

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]);