Feedback: package polices code?
- Dominant language
- Python
- Stars
- 7.5k
- Forks
- 424
- PR merge metrics
- No merged PRs in 30d
Description
I discovered `pipreqs` via [this SO answer](https://stackoverflow.com/a/31684470/3333992), and it seemed like just what I needed... except for the fact that it polices my code? I have a big set of non-production-level code for which I wanted a `requirements.txt`. While running `pipreqs` on my target folder, I kept getting errors like `IndentationError: unexpected indent` or `IndentationError: unexpected indent`. I can't polish the code now, I just need someone else to be able to replicate my environment and run the code by checking only for the modules I use, otherwise I would just go for `pip freeze`.
I don't see an option to run `pipreqs` in non-linting mode, is there one? In any case, it would also be useful to have this behavior documented somewhere.
Contributor guide
Research direction
Start with pipreqs' command-line handling and the code that parses Python files in the target folder; the issue does not name specific files or tests. Check whether a non-linting mode exists and how parsing errors are handled. Done means malformed or non-production code can be processed as requested, with the behavior documented if an option is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100