issue_comments
6 rows where issue = 435532136 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Support from reading unformatted Fortran files · 6 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
753304428 | https://github.com/pydata/xarray/issues/2911#issuecomment-753304428 | https://api.github.com/repos/pydata/xarray/issues/2911 | MDEyOklzc3VlQ29tbWVudDc1MzMwNDQyOA== | sjvrijn 8833517 | 2021-01-01T11:25:53Z | 2021-01-01T11:25:53Z | CONTRIBUTOR | @tomchor For small snippets including it directly into the docs seems best to me, but an explicit link to the commit/file seems fine too. I've seen links to github issues and blog posts in the docs, so linking to a commit for a larger piece of code doesn't seem out of the ordinary to me. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support from reading unformatted Fortran files 435532136 | |
489873332 | https://github.com/pydata/xarray/issues/2911#issuecomment-489873332 | https://api.github.com/repos/pydata/xarray/issues/2911 | MDEyOklzc3VlQ29tbWVudDQ4OTg3MzMzMg== | tomchor 13205162 | 2019-05-07T01:41:15Z | 2019-05-07T01:41:15Z | CONTRIBUTOR | Wrote a simple function here. I'm not sure what the best to link this to the docs is, since I can't guarantee that this function will change in the future. Maybe link the commit? Or maybe just straight up pasting that into the docs with a small example script using it? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support from reading unformatted Fortran files 435532136 | |
485497857 | https://github.com/pydata/xarray/issues/2911#issuecomment-485497857 | https://api.github.com/repos/pydata/xarray/issues/2911 | MDEyOklzc3VlQ29tbWVudDQ4NTQ5Nzg1Nw== | dcherian 2448579 | 2019-04-22T18:08:24Z | 2019-04-22T18:08:24Z | MEMBER | I think "Reading and writing files" would be most appropriate :smiley: https://xarray.pydata.org/en/stable/io.html Adding a new section on "binary fortran files" and linking to xgcm, xbpch and your code would be great. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support from reading unformatted Fortran files 435532136 | |
485473367 | https://github.com/pydata/xarray/issues/2911#issuecomment-485473367 | https://api.github.com/repos/pydata/xarray/issues/2911 | MDEyOklzc3VlQ29tbWVudDQ4NTQ3MzM2Nw== | tomchor 13205162 | 2019-04-22T16:49:46Z | 2019-04-22T16:49:57Z | CONTRIBUTOR | @dcherian That's a good idea. At the moment my implementation is very problem-specific so it's not good to upload that. Generalizing it is very straightforward though (albeit a bit of work), but I'll try to do that soon. I wonder what the best place for that in the docs would be. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support from reading unformatted Fortran files 435532136 | |
485465406 | https://github.com/pydata/xarray/issues/2911#issuecomment-485465406 | https://api.github.com/repos/pydata/xarray/issues/2911 | MDEyOklzc3VlQ29tbWVudDQ4NTQ2NTQwNg== | dcherian 2448579 | 2019-04-22T16:22:45Z | 2019-04-22T16:22:45Z | MEMBER |
+1. Maybe put up your example implementation on github/gitlab, and we can link to it from the documentation? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support from reading unformatted Fortran files 435532136 | |
485272748 | https://github.com/pydata/xarray/issues/2911#issuecomment-485272748 | https://api.github.com/repos/pydata/xarray/issues/2911 | MDEyOklzc3VlQ29tbWVudDQ4NTI3Mjc0OA== | darothen 4992424 | 2019-04-21T18:32:56Z | 2019-04-21T18:32:56Z | NONE | Hi @tomchor, it's not too difficult to take the readers that you already have and two wrap them in such a way that you can interact with them via xarray; you can check out the packages xgcm or xbpch for examples of this can work in practice. I'm not sure if a more generic reader is within or beyond the scope of the core xarray project, though... although example implementations and writeups would make a great contribution to the community! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support from reading unformatted Fortran files 435532136 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 4