Optional dependency for different storages?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 206
- PR merge metrics
- No merged PRs in 30d
Description
🚀 Feature Request
Although we support many kinds of storages, actually we only use one kind of them. So it would be great if we have different storages as different groups of optional dependencies. I have to admit this will bring back-compatibility issue. Just a head up here whether this could be possible to happen.
Motivation
We are migrating our code base from stratch and finding that streaming dataset introduces a lot of dependencies that we will not likely to use in the near future.
[Optional] Implementation
Additional context
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
The issue names no files, tests, or entry points. Start by locating the package's dependency and storage configuration, then determine how storage-specific optional groups could be defined without breaking existing installations. Done means the proposal has an agreed dependency grouping and compatibility approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100