aboutcode-org / aboutcode-org/scancode-toolkit

Vendor some key libraries

Open
#3,192 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
2.6k
Forks
791
Avg merge
1d 12h
Merged PRs (30d)
5

Description

As a fix for https://github.com/nexB/scancode-toolkit/issues/3179 a solution is to vendor the libraries with objects that participate in the license index pickle such that we are not dependent on their uncontrolled updates. These include:

- attrs
- intbitset and pyahocorasick: these are native libraries and are low priority since we are maintaining them and are able to control their release cycle
- license_expression and boolean.py though we maintain these, so low priority (used for the Rule.license_expression_object)

See also these related issues:
- https://github.com/nexB/scancode-toolkit/issues/3190
- https://github.com/nexB/scancode-toolkit/issues/3191
- https://github.com/nexB/scancode-toolkit/issues/3179

Note: we are doing vendoring in https://github.com/nexB/typecode/blob/main/README.rst with vendy for pygments and also FetchCode (inherit from pip) and tracecode-toolkit-strace (using vendorize for altgraph and docopt). python-vendorize seems mostly current and upda to date.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.