Should Xarray prefer h5netcdf and scipy to netCDF4?
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?
https://github.com/pydata/xarray/pull/10656 unifies the choose of default engine parameter for reading and writing netCDF files. This is a breaking change, so it's worth considering if we want to bundle in any other related changes.
I think it might make sense to switch the default netCDF engine to chosen from the first valid choice of (h5netcdf, scipy, netCDF4), rather than the current order of (netCDF4, h5netcdf, scipy), because netCDF is generally a bit slower than the other libraries, and plays less nicely with concurrency (because it's written in C rather than Python).
Any thoughts?
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 reviewing pull request #10656, which unifies the default engine selection for reading and writing netCDF files. Compare the proposed (h5netcdf, scipy, netCDF4) order with the current order and assess the stated performance and concurrency tradeoffs; done means reaching and recording a decision about whether the default order should change.
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