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.

@nnobelis nnobelis force-pushed the nnobelis/non_empty_install_requires branch from df95e22 to 4ecf5cd Compare October 16, 2025 05:56
@MarcelBochtler MarcelBochtler force-pushed the nnobelis/non_empty_install_requires branch 2 times, most recently from 823421c to 8826952 Compare October 22, 2025 14:10
MarcelBochtler and others added 2 commits October 22, 2025 16:18
Signed-off-by: Marcel Bochtler <[email protected]>
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]>
@MarcelBochtler MarcelBochtler force-pushed the nnobelis/non_empty_install_requires branch from 8826952 to 708b3be Compare October 22, 2025 14:18
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

2 participants