aboutcode-org / aboutcode-org/scancode-toolkit

Please clarify what the scancode-toolkit*-mini* distribution is

未關閉
#3,432 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Python
星號
2.6k
分支
791
平均合併
1 天 12 小時
30 天內合併 PR
5

描述

I'm have a hard time understanding this:

https://github.com/nexB/scancode-toolkit/blob/a29ae817d95296146ba8ac5bd94ed043d541cdc6/setup-mini.cfg#L7

> pre-built binary dependencies

What exactly are these? To me, Python bytecode is also binary, so any *wheel* for a Python package is a pre-built binary dependency in my view. And if "pre-built binary dependencies" are omitted with *mini*, what are they being substituted with? Because their functionality must somehow be replaced.

Asking differently, what's the difference between using the *mini* distribution, and installing (full) *scancode-toolkit* with `pip install --no-binary=:all:`?

> These are instead installed separately

How?

> or with the extra_requires scancode-toolkit-mini[full]

This is even more confusing: What's the difference between installing `scancode-toolkit-mini[full]` and `scancode-toolkit` in the first place?

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。