issue_comments: 667637217
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/issues/4285#issuecomment-667637217 | https://api.github.com/repos/pydata/xarray/issues/4285 | 667637217 | MDEyOklzc3VlQ29tbWVudDY2NzYzNzIxNw== | 6213168 | 2020-08-02T06:56:23Z | 2020-08-02T06:56:23Z | MEMBER | I think that xarray should offer a "compatibility test toolkit" to any numpy-like, NEP18-compatible library that wants to integrate with it. Instead of having a module full of tests specifically for pint, one for sparse, one for cupy, one for awkward, etc. etc. etc. those projects could just write a minimal test module like this: ```python import xarray import sparse xarray.testing.test_nep18_module( sparse, # TODO: lambda to create an array # TODO: list of xfails ) ``` which would automatically expand into a comprehensive suite of tests thanks to pytest parameterize/fixture magic. this would allow developers of numpy-like libraries to just test their package vs what's expected from a generic NEP-18 compliant package. |
{ "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
667864088 |