activate script created by venv is not smart enough
Open
Nobody has claimed this yet.
3.10
3.8 (EOL)
3.9 (EOL)
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41256 |
|---|---|
| Nosy | @vsajip, @ericvsmith, @jdevries3133 |
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-07-09.09:57:08.188>
labels = ['3.8', 'library', '3.9', '3.10']
title = 'activate script created by venv is not smart enough'
updated_at = <Date 2021-07-23.18:17:44.709>
user = 'https://bugs.python.org/kunaltyagi'
bugs.python.org fields:
activity = <Date 2021-07-23.18:17:44.709>
actor = 'jack__d'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-07-09.09:57:08.188>
creator = 'kunaltyagi'
dependencies = []
files = []
hgrepos = []
issue_num = 41256
keywords = []
message_count = 4.0
messages = ['373386', '373485', '398085', '398086']
nosy_count = 4.0
nosy_names = ['vinay.sajip', 'eric.smith', 'kunaltyagi', 'jack__d']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue41256'
versions = ['Python 3.8', 'Python 3.9', '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 with the migrated BPO issue 41256 and the Python standard-library venv component. The payload names no file, failing test, expected activation behavior, or acceptance criteria, so clarify what “smart enough” should mean before locating the relevant activation scripts and tests. Done should include a documented expected behavior and verification for it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100