Tracking internal uses of concat that don't allow setting all the kwargs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 14
Description
What is your issue?
While working on #8778 I encountered some places where concat is used internally but the kwargs are not individually settable: stack and groupby.
#10062 hardcodes them to the old defaults: data_vars="all", coords="different", compat="equals", join="outer"
@dcherian mentioned (https://github.com/pydata/xarray/pull/10062/files#r1978040669) that we might want stricter behavior.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the internal concat uses in stack and groupby, then compare their hardcoded defaults with #10062 and the discussion linked from #8778. The issue needs a decided scope for individually settable kwargs and stricter behavior; completion should cover the identified uses consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100