pymc-devs / pymc-devs/pymc-examples
update `requirements-write.txt`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 398
- Forks
- 325
- Avg merge
- 9d 15m
- Merged PRs (30d)
- 1
Description
The current requirements file is out of date and potentially too minimal
Todo
- Replace
pymc3withpymc, possibly with a>=4.0version tag. - We don't need to have total coverages of all packages used in the repo, but it would be helpful to add more commonly used packages such as:
matplotlibnumpyxarrayseabornbambijupyterlab-code-formatter,isort(useful when writing notebooks in the browser, rather than VS Code for example)patsyscipydaft(for making causal DAG's)
- Check version on
pre-commitis still appropriate - Update instructions in final section of the contributing guide to include the instructions on how to build a
pymc-examples-envenvironment. E.g.conda create --name pymc-examples-env --file requirements-write.txt
Happy to take feedback on this of course.
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 with requirements-write.txt and the final section of CONTRIBUTING.md. Compare the listed dependencies and pre-commit version with the repository's current needs, then verify the documented conda create command. Done means the requested packages and PyMC entry are updated and the contributing instructions describe the pymc-examples-env setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, documentation, tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100