issue_comments: 54416883

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/25#issuecomment-54416883 https://api.github.com/repos/pydata/xarray/issues/25 54416883 MDEyOklzc3VlQ29tbWVudDU0NDE2ODgz 1217238 2014-09-04T06:50:49Z 2014-09-04T06:50:49Z MEMBER

I'm going to close this issue as fixed, but feel free to complain if you feel otherwise (particularly if you have ideas for how we should improve this).

The rule that we seem to have settled on is that xray will either drop all attributes if the result could be ambiguous, or, if there is a clear priority, it will only keep around attributes from the first object. The one firm rule is that xray does not do any checking of attributes for conflicts.

Unless compat == 'identical', there's no checking for conflicts: operations are either keep them all (mostly just subsetting/indexing) or drop them all. For some unary operations like mean, an option keep_attrs allows for switching the default from "drop" to "keep". Binary mathematical operations like * are always "drop".

In cases where there are two objects to combine but where the priority is clearer (e.g., in concat and merge), we'll preserve attributes from the first object and ignore the second. We use the same rule for in-place binary operations.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   28376794