pull_requests: 98409580
This data as json
id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
98409580 | MDExOlB1bGxSZXF1ZXN0OTg0MDk1ODA= | 1169 | closed | 0 | DOC: small improvements to the netCDF docs | 10050469 | Partly addresses https://github.com/pydata/xarray/issues/768#issuecomment-187226020 and https://github.com/pydata/xarray/issues/1154, mostly by making the tone less defensive. I also added that we recommend the netCDF format for IO. (I think that the format is powerful enough for being useful in other disciplines than geosciences). I agree with @rabernat that the current page title (Serialization and IO) could be changed to something more accessible, but I don't know how. Two possibilities, both quite long (it looks a bit ugly on RTD): - "Reading and writing xarray data structures on disk" - "Reading/writing xarray data structures" | 2016-12-16T21:58:17Z | 2016-12-24T11:54:51Z | 2016-12-24T11:54:51Z | 2016-12-24T11:54:51Z | 88cc396f5117c09c76e15d6383aeca32b4d4a8bd | 0 | 32f95307a792a72cbb1d534542f906159f144e10 | 89a6732346542b234c0c655034c6e0ab49fecc56 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/1169 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests