venv: make binary or library from C/C++ installable to `./venv/bin/` or `./venv/lib/`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
Feature or enhancement
Make C/C++ library or executable which the python library relied on be able to be installed into ./.venv/lib or ./.venv/bin where ./.venv is the path to virtual env root.
Also ./.venv/include/.
As a result, it can be more flexible to add additional C/C++ dependency without system supervisor permission.
Pitch
Sometimes, python libraries depend C/C++ libraries. Currently, the C/C++ library need to installed system wide. It is a great inconvenience.
If a required C/C++ library is not provided by Linux distro. Just install it into virtual env directory without polluting system-wide environment.
For executable, nothing is needed for functionality. For library, it would be solvable by properly setting LIBRARY_PATH and LD_LIBRARY_PATH.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how virtual environments currently handle native libraries, executables, and headers, with attention to .venv/bin, .venv/lib, and .venv/include. Define the installation and environment-variable behavior needed for C/C++ dependencies, then identify the relevant tests and documentation before implementation; done means a Python package can use such dependencies without system-wide installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, python
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100