explosion / explosion/spacy-ray
update ray dependency to <2.0.0
- Dominant language
- Python
- Stars
- 55
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
ray 1.9.1 was released last week, and with it windows support has moved from "alpha" to "beta" quality. It would help the ray project if more people could try out the newer version. spacy-ray pins the maximum ray version to [`ray<1.0.0`](https://github.com/explosion/spacy-ray/blob/6c6ca8c11932d6ba51abda442f01b765f1d6e509/setup.cfg#L32). Are there known problems preventing bumping that up to `ray<=1.9.1` ?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in setup.cfg at the dependency constraint linked in the issue and compare the requested upper bounds in the title and body. Check the project’s compatibility with Ray 1.9.1 and look for known problems before changing the constraint. Done means the supported Ray range is updated consistently, or a specific incompatibility is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, machine-learning
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100