Clarify Python library usage and document current ScanCode limitations#4713
Clarify Python library usage and document current ScanCode limitations#4713vidhiii1711 wants to merge 2 commits intoaboutcode-org:developfrom
Conversation
|
Coming from the perspective of an actual API user, the following aspects are not clear to me:
In general, it seems like the docs proposed for this issue in #4473 seem more reasonable. |
|
@stefan6419846 Thanks for the detailed feedback — that’s very helpful. I took a conservative approach while documenting this because I couldn’t find an officially documented, supported scan API and wanted to avoid presenting an example that might be misleading for new users. That said, your point about long-term practical usage of scancode.api makes sense. I’m happy to revise the documentation to include a concrete, real-world example based on commonly used APIs if that’s preferred. I’ll also revisit the installation section and clarify why a full install is currently recommended. If you have a specific example or pattern you’d recommend (similar to what’s discussed in #4473), I’d be glad to align the docs with that approach. |
Fixes #3130
Tasks
Testing
-> Verified ScanCode modules can be imported successfully
-> Relevant tests were run locally
-> Full test suite was not executed due to long runtime
Signed-off-by: Vidhi Singh [email protected]