bndr / bndr/pipreqs

[Bug] The requirement.txt is always empty while the concern pkgs are collected by pipreqs cli

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

Description

System: win 11 22621.3737
python: 3.10
pipreqs: 0.5.0

cli cmd: `pipreqs F:\AdaBins --encoding=utf8 --scan-notebooks --force`

The version infos are pasted above. I run the cli cmd in command line and get the normal standard output but the requirements.txt saved is empty.

please fix this bug soon

Contributor guide

Open the contributing guide

Research direction

Start with the pipreqs CLI entry point and reproduce `pipreqs F:\AdaBins --encoding=utf8 --scan-notebooks --force` on Python 3.10 and Windows 11. Check why the collected packages do not reach the generated requirements.txt; done means the command produces a non-empty file matching the project's imports.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.