issues: 594790230

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
594790230 MDU6SXNzdWU1OTQ3OTAyMzA= 3940 ENH: Support more of the pandas str accessors 2272878 closed 0     1 2020-04-06T04:18:32Z 2021-03-11T17:49:32Z 2021-03-11T17:49:32Z CONTRIBUTOR      

Currently pandas supports a lot of str accessors that xarray doesn't. Many of them have useful functionality. I think it would be good if the xarray had more of these str accessors. I would be willing to begin working on this.

There seem to be three categories. One that has a one-to-one mapping between input and output (so one input element becomes one output element), and one that has a one-to-many mapping (one input element becomes multiple output elements), and one that has a many-to-one mapping (multiple input elements become one output element). Exactly how the one-to-many mapping should be handling, if at all, is an open issue. Some of the many-to-one mappings (specifically join) would need a dimension argument.

One-to-one

  • [x] casefold(self)
  • [x] normalize(self, form)

One-to-many

  • [x] extract(self, pat[, flags, expand])
  • [x] extractall(self, pat[, flags])
  • [x] findall(self, pat[, flags])
  • [x] get_dummies(self[, sep])
  • [x] partition(self[, sep, expand])
  • [x] rpartition(self[, sep, expand])
  • [x] rsplit(self[, pat, n, expand])
  • [x] split(self[, pat, n, expand])

Many-to-one

  • [ ] cat(self[, others, sep, na_rep, join])
  • [ ] join(self, sep)
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3940/reactions",
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 1,
    "rocket": 0,
    "eyes": 0
}
   completed 13221727 issue

Links from other tables