home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 789910109

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/pull/4835#issuecomment-789910109 https://api.github.com/repos/pydata/xarray/issues/4835 789910109 MDEyOklzc3VlQ29tbWVudDc4OTkxMDEwOQ== 13301940 2021-03-03T17:29:15Z 2021-03-03T17:30:42Z MEMBER

Is there a particular reason why we're moving away from nbsphinx?

I got a bit carried away when I saw the Markdown design document in https://github.com/pydata/xarray/pull/4979 :). I figured with myst/myst-nb, it would be easier to support documentation source written in any format (.md, .rst, .ipynb) in the future. I will revert back to nbsphinx ((the switch is probably not yet worth it).

unrelated to that: the internals page is a collection of mostly unrelated topics. It might be good to break it up into separate pages (e.g. "Variable", "duckarray integration", "accessors", "zarr spec", "custom backends", etc.)

👍🏽. I am going to separate them into different pages

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  790677360
Powered by Datasette · Queries took 4.589ms · About: xarray-datasette