Skip to content

Conversation

nnobelis
Copy link

Sometimes, when the --analyze-setup-py-insecurely parameter is used, the requirements resolution can contain some empty elements. For instance for gnupg-2.3.1/gnupg-2.3.1/setup.py, the requirements are resolved to ['psutil>=1.2.1', '']. The second element of this array crashes the Python Inspector.
This commit fixes the issue by removing empty elements from the array.

Resolves #247.

Sometimes, when the `--analyze-setup-py-insecurely` parameter is used,
the requirements resolution can contain some empty elements. For
instance for gnupg-2.3.1/gnupg-2.3.1/setup.py, the requirements are
resolved to ['psutil>=1.2.1', '']. The second element of this array
crashes the Python Inspector.
This commit fixes the issue by removing empty elements from the array.

Resolves aboutcode-org#247.

Signed-off-by: Nicolas Nobelis <[email protected]>
@nnobelis nnobelis force-pushed the nnobelis/non_empty_install_requires branch from df95e22 to 4ecf5cd Compare October 16, 2025 05:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Python Inspector crashes on requirement gnupg==2.3.1

1 participant