-
-
Notifications
You must be signed in to change notification settings - Fork 562
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
Running scancode-license-data
without arguments does not work
#4024
Comments
scancode-license-data
does not workscancode-license-data
withouot arguments does not work
@sschuberth please refer to the help text for the command:
The code is at https://github.com/aboutcode-org/scancode-toolkit/blob/develop/src/licensedcode/license_db.py#L208 btw, as indicated in the traceback. I think you are not providing the
Maybe this confusion was caused by inadequate docs? This should probably be included in https://scancode-toolkit.readthedocs.io/en/stable/cli-reference/other-commands.html which is at https://github.com/aboutcode-org/scancode-toolkit/blob/develop/docs/source/cli-reference/other-commands.rst If you can confirm this, it would be great. We can then convert the issue to enhance the docs on this. |
scancode-license-data
withouot arguments does not workscancode-license-data
without arguments does not work
I can confirm that both |
We could add more documentation as suggested in #4024 (comment) and probably print a statement to provide path/nudge towards running the help text if someone does not provide a path. |
As no one reads docs, I indeed recommend to "build-in the docs" by making the tool print something meaningful in this case. Thanks! |
The simplest way is to make the option required with a
|
could you look at my pr and see if its fit for merging #4029 |
Description
Running
scancode-license-data
that comes with 32.3.0 does not work.How To Reproduce
scancode-toolkit
version 32.3.0.scancode-license-data
without any arguments.The same happens on another machine with Python 3.13:
System configuration
pip install
.The text was updated successfully, but these errors were encountered: