-
Notifications
You must be signed in to change notification settings - Fork 24
TypeError: cannot unpack non-iterable NoneType object #72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
72.json.txt @mnonnenmacher I was not able to reproduce this error for requirements.txt, uploading the result here |
@mnonnenmacher I ran the command with the verbose flag like this |
@TG1999 Thanks, that works for me as well. I think it would be great if the tool would print a meaningful error message also without the |
For the release notes see [1]. To fix the analysis of `setup.py` files, always enable the new option `--analyze-setup-py-insecurely`. This will be made configurable in a later commit. The option is required for some tests projects where this analysis would fail otherwise [2]. [1]: https://github.com/nexB/python-inspector/blob/main/CHANGELOG.rst#v071 [2]: aboutcode-org/python-inspector#72 Signed-off-by: Martin Nonnenmacher <martin.nonnenmacher@bosch.io>
For the release notes see [1]. To fix the analysis of `setup.py` files, always enable the new option `--analyze-setup-py-insecurely`. This will be made configurable in a later commit. The option is required for some tests projects where this analysis would fail otherwise [2]. [1]: https://github.com/nexB/python-inspector/blob/main/CHANGELOG.rst#v071 [2]: aboutcode-org/python-inspector#72 Signed-off-by: Martin Nonnenmacher <martin.nonnenmacher@bosch.io>
For the release notes see [1]. To fix the analysis of `setup.py` files, always enable the new option `--analyze-setup-py-insecurely`. This will be made configurable in a later commit. The option is required for some tests projects where this analysis would fail otherwise [2]. [1]: https://github.com/nexB/python-inspector/blob/main/CHANGELOG.rst#v071 [2]: aboutcode-org/python-inspector#72 Signed-off-by: Martin Nonnenmacher <martin.nonnenmacher@bosch.io>
For the release notes see [1]. To fix the analysis of `setup.py` files, always enable the new option `--analyze-setup-py-insecurely`. This will be made configurable in a later commit. The option is required for some tests projects where this analysis would fail otherwise [2]. [1]: https://github.com/nexB/python-inspector/blob/main/CHANGELOG.rst#v071 [2]: aboutcode-org/python-inspector#72 Signed-off-by: Martin Nonnenmacher <martin.nonnenmacher@bosch.io>
@mnonnenmacher we can have an issue to track this if you want. |
@pombredanne Yes, that would be nice, I think that would be a better UX. |
With python-inspector 0.7.0, when running
python-inspector --python-version 310 --json-pdt - --requirement requirements.txt
on this file I get this error:The same happens with
python-inspector --python-version 27 --json - --setup-py setup.py
and this file.The text was updated successfully, but these errors were encountered: