pymc-devs / pymc-devs/pytensor
Add upper bounds for all versions, and test accordingly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 644
- Forks
- 208
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 16
Description
Description
We release frequently enough that I believe it's feasible to have upper and lower bounds for all direct dependencies. This will help prevent breakage that sometimes comes with new Numpy versions, new Python versions, or similar. This isn't completely foolproof since there might be problems with transitive dependencies. But I think it would go a long ways towards preventing a lot of very unpleasant incidents.
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
Review the project's direct dependency declarations and existing dependency-related tests. Add upper and lower bounds for every direct dependency, including dependencies affected by new NumPy or Python versions, and update the tests accordingly. Done means the direct dependencies are bounded and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100