An invalid `requirements.txt` file is silently accepted

Open
#178 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reproducing the issue with the shown requirements.txt content and compare it with plain pip's invalid-requirement behavior. Trace the requirements.txt handling entry point; done means malformed content is rejected with an error instead of producing an empty dependency list, with coverage for the example.

Written by the indexing model from the issue text.

Description

If requirements.txt contains wrongly formatted content like

Package         Version
--------------- -----------
wheel           0.41.2

then PI accepts this without any error but returns no dependencies. Plain pip would say

ERROR: Invalid requirement: 'Package         Version' (from line 1 of requirements.txt)
Dominant language
Python
Stars
23
Forks
29
Avg merge
1h 7m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/python-inspector

All issues in aboutcode-org/python-inspector

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.