Pipreqs generates bad requirement besides pymongo
Open
- Dominant language
- Python
- Stars
- 7.5k
- Forks
- 424
- PR merge metrics
- No merged PRs in 30d
Description
I'm generating the requirements for a project that uses the **pymongo** library and it seems that pipreqs also generates the following requirement, which is invalid:
`~ymongo==4.1.1`
Contributor guide
Research direction
Reproduce pipreqs on a project that imports pymongo and inspect the generated requirements entry. Trace how the dependency name is derived and ensure the output contains the valid pymongo requirement rather than ~ymongo==4.1.1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100