Python SDK build process leaks tox dependency into user space
Open
core
improvement
P3
python
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
The current build process of the python SDK should be fully contained in a virtualenv, at this moment the tox dependency is not correctly contained and end up installed in the user account.
Imported from Jira [BEAM-1733](https://issues.apache.org/jira/browse/BEAM-1733). Original Jira may contain additional context.
Reported by: iemejia.
Contributor guide
Research direction
Start by locating the Python SDK build process and reproduce the build in a clean environment, checking where tox is installed. Done means the build remains contained in its virtualenv and does not install the tox dependency into the user's account.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100