bazel-contrib / bazel-contrib/rules_python
doc how to setup dev vs non-dev pypi dependencies
Open
Good first issue
type: documentation
type: pip
- Dominant language
- Starlark
- Stars
- 688
- Forks
- 721
- Avg merge
- 15h 7m
- Merged PRs (30d)
- 76
Description
It's common for projects to have dev-only dependencies. We should document how to do similar using pip.parse.
The basic steps are:
* Have a separate `@dev_pypi` hub
* Separate requirements.txt files
* Separate compile_pip_requirements/uv.lock (or equiv)
Contributor guide
Research direction
Start by locating the existing documentation and examples for pip.parse. Document the separate @dev_pypi hub, separate requirements.txt files, and separate compile_pip_requirements/uv.lock files; done means a newcomer can follow the documented setup for development and non-development dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100