realpython / realpython/python-guide
Confusion between package management solution and project structure
Nobody has claimed this yet.
- Dominant language
- Batchfile
- Stars
- 29.8k
- Forks
- 5.9k
- PR merge metrics
- No merged PRs in 30d
Description
I got a little bit confused when reading recommendation for package management solution and project structure.
Package management section recommends pipenv (thanks for that :)), but then project structure recommends requirements.txt file in the root.
Is that suggesting I should be using pipenv, but exporting dependencies in pip compatible format?
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
Compare the package management and project structure sections described in the issue, starting with their recommendations for Pipenv and requirements.txt. Done means the guide clearly explains whether these recommendations are compatible and how a reader should interpret them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100