pymc-devs / pymc-devs/pytensor
Use environment.yml (or something like that) in CI
Open
Nobody has claimed this yet.
GitHub CI/CD
help wanted
- Dominant language
- Python
- Stars
- 644
- Forks
- 208
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 16
Description
Description
The CI dependencies are completely dissociated from the conda pytensor-dev environment specified by environment.yml.
This led to need a separate commit in #448 that should have gone into #446
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 comparing environment.yml with the dependency setup at lines 139-152 of .github/workflows/test.yml, then read the surrounding workflow. The work is done when CI dependencies are aligned with the conda environment definition or an agreed equivalent, and the test workflow passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100