issue_comments: 243289800
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/988#issuecomment-243289800 | https://api.github.com/repos/pydata/xarray/issues/988 | 243289800 | MDEyOklzc3VlQ29tbWVudDI0MzI4OTgwMA== | 1217238 | 2016-08-29T23:35:35Z | 2016-08-29T23:35:35Z | MEMBER | I agree that end users are likely to set this flag unilaterally, especially for interactive use. That's fine. This could even be OK in a higher level library, though I would encourage requiring an explicit opt in application code. One thing to consider is whether to allow multiple attribute handlers to be registered simultaneously or not. I kind of like a set_options interface that requires all handlers to be registered at once (as opposed to adding handlers incrementally ), because that ensures conflicts cannot arise inadvertantly. Either way, I don't think the performance penalty here would be significant in most cases, given how much of Python's dynamic nature xarray already uses. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
173612265 |