bndr / bndr/pipreqs

Malformed requirements.txt created

Open
#504 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
7.5k
Forks
424
PR merge metrics
No merged PRs in 30d

Description

I created my requirements.txt using the following command:

`pipreqs . --force --ignore ".venv"`

I used `--force` because the project has an existing, incomplete requirements.txt, which is how I found pipreqs in the first place.
I used `--ignore ".venv"` because i encountered an error related to this [issue](https://github.com/bndr/pipreqs/issues/214).

The requirements.txt now contains duplicates such as:
...
PyYAML==6.0.2
PyYAML==6.0.2
...

conflicting versions:
...
pywin32=310
pywin32==311

as well as wrong library names:
...
skimage==0.0
...
(should be scikit-image)

I am on windows, using python 3.12.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the `pipreqs . --force --ignore ".venv"` command on Windows with Python 3.12, focusing on the generated requirements.txt. Investigate how duplicate entries, conflicting versions, and imported names such as `skimage` are produced; done means the output contains one correct, valid requirement for each dependency.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.