indygreg / indygreg/PyOxidizer

Can't use opencv-python due to --no-binary

Open
#102 4 comments 1 reaction 0 assignees View on GitHub
need-info
Dominant language
Rust
Stars
6.2k
Forks
256
PR merge metrics
No merged PRs in 30d

Description

Our requirement file has, among other packages:
```
opencv-python==3.3.0.9
```
However, pip-requirements-file and pip-install-simple use the `--no-binary :all:` option when calling `pip`.

Is there any option to download the packages anyway?

I saw this was introduced in v0.2.0, I'm trying version v0.1.3 now.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the requirement-file and install entry points named pip-requirements-file and pip-install-simple, including where pip is invoked with --no-binary :all:. Compare the behavior introduced in v0.2.0 with v0.1.3 and determine what change would allow opencv-python==3.3.0.9 to be downloaded; done means the package can be handled through the requirement file.

Written by the indexing model from the issue text.

Assessment

Tech stack
opencv, python
Domain
build-system
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.