pypa / pypa/packaging.python.org
Move from the Application Dependency management tutorial to a guide page instead
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 4
Description
See #912 for full context.
The idea is to present the available dependency management tooling options as a gradient of increasing complexity + scope-of-tooling -- as done in Installing Scientific Packages -- putting things like manually managed pip requirements.txt files, pip-tools, pipenv and poetry on "equal" footing; moving away from a guided tutorial to using pipenv to being a guide on how to pick the right option for you.
Contributor guide
No contributing guide indexed for this repository
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 the existing Application Dependency management tutorial and read issue #912 for the full context. Use the Installing Scientific Packages guide as the stated model, then review how manually managed pip requirements.txt files, pip-tools, pipenv, and poetry can be presented on equal footing. Done means the tutorial has become a guide that helps readers choose among options by complexity and scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100