Allow inheritance of Venvs
Open
Nobody has claimed this yet.
stdlib
topic-venv
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42101 |
|---|---|
| Nosy | @Carreau |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2020-10-20.21:18:09.031>
labels = ['type-feature', '3.10']
title = 'Allow inheritance of Venvs'
updated_at = <Date 2020-11-25.02:00:03.340>
user = 'https://github.com/Carreau'
bugs.python.org fields:
activity = <Date 2020-11-25.02:00:03.340>
actor = 'mbussonn'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2020-10-20.21:18:09.031>
creator = 'mbussonn'
dependencies = []
files = []
hgrepos = []
issue_num = 42101
keywords = ['patch']
message_count = 1.0
messages = ['379164']
nosy_count = 1.0
nosy_names = ['mbussonn']
pr_nums = ['23504']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue42101'
versions = ['Python 3.10']
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 reviewing the original BPO issue 42101 and the referenced pull request python/cpython#23504, since the migrated issue text contains no implementation details or file paths. Determine the expected behavior for allowing Venv inheritance from those records, then run the relevant virtual-environment tests identified there and confirm that inheritance works as specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100