See introductory video for GSoC here: https://www.aboutcode.org/news/2022-03-30-aboutcode-for-gsoc2022.html and https://github.com/nexB/aboutcode/wiki/GSOC-2023 - Weekly meeting on Monday's at 16:00 UTC on Jitsi. See details and URL at https://github.com/nexB/aboutcode/wiki/MeetingMinutes - Interested in contributing? See https://aboutcode.readthedocs.io/en/latest/contributing.html - If you need support specifically for ScanCode ask in https://gitter.im/aboutcode-org/scancode
dependabot[bot] on pip
Bump cryptography from 36.0.2 t… (compare)
The wiki page took too long to render. Please edit this wiki page’s content so it renders faster.
sometimes. Should we make this a year-wise page instead?
@lf32 I could not reproduce you ScanCode TK Apple M1 installation issue. Can you try again and if this happens again, please create an issue
I've already tried doing unzip tar -> ./scancode --help thrice :/
nexB/scancode-toolkit#3061
is there someone else who has m1 mac
AdditionalLicenseLocationProvider
or something and having the path providers for additional licenses subclass that. What are your thoughts?--summary
feature: it seems to be a summary for the root, not faceted by package
licenses_reference[].text_urls
and text licenses_reference[].text
--report
argument
pip-requirements-parser
to fix this
@aspacca re: pip requirements parser... it does parse the same way that pip parses. But it does NOT lookup in remote PyPI repos .
See https://github.com/nexB/python-inspector for this IMHO
parser-wise there is nothing to do there as we cannot know if a requirement exists or not.
The inspector does reuse pip-requirements-parser and resolve deps and interacts with PyPI repos alright and this would be the place IMHO.
I created nexB/python-inspector#64 ...