Make our Python pom files virtualenv-compatible.
Open
bug
build
P3
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
The importance of this may depend on whether we recommend or discourage using mvn at all for Python, see also https://issues.apache.org/jira/browse/BEAM-2340
Imported from Jira [BEAM-2341](https://issues.apache.org/jira/browse/BEAM-2341). Original Jira may contain additional context.
Reported by: robertwb.
Contributor guide
Research direction
The issue names no files or tests. Start by reviewing the linked BEAM-2340 context and locating the Python pom files; determine the expected virtualenv behavior before changing them. Done means the Maven-based Python setup works inside a virtualenv and the relevant validation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100