Should `open_mfdataset` try to guess which engine to use?
Open
Nobody has claimed this yet.
design question
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 14
Description
What is your issue?
The guess_can_open logic in backends can be hard to get right. It is certainly helpful to be able to guess an engine when opening a single file, but when you are opening a whole bunch of files you probably should explicitly set the engine.
I guess the action on this ticket would be to make the engine kwarg required on open_mfdataset.
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 locating the open_mfdataset entry point and reading its current engine-handling path. Check how the existing backend guessing behavior is covered by tests; the work is done when the intended engine requirement is enforced consistently and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100