Refactor the test_runpy walk_package support code into a common location
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
Research direction
Start by locating the walk_package support code in test_runpy and review dependencies 15403 and 15415 for the intended common location. Run the relevant test_runpy tests; done means the support code has been moved to a shared location without changing test behavior.
Written by the indexing model from the issue text.
Description
| BPO | 15376 |
|---|---|
| Nosy | @ncoghlan, @cjerdonek, @ericsnowcurrently |
| Dependencies |
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 2012-07-17.07:10:48.923>
labels = ['easy', 'type-feature', 'tests']
title = 'Refactor the test_runpy walk_package support code into a common location'
updated_at = <Date 2019-03-15.21:57:39.861>
user = 'https://github.com/cjerdonek'
bugs.python.org fields:
activity = <Date 2019-03-15.21:57:39.861>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2012-07-17.07:10:48.923>
creator = 'chris.jerdonek'
dependencies = ['15403', '15415']
files = []
hgrepos = []
issue_num = 15376
keywords = ['easy']
message_count = 8.0
messages = ['165683', '165702', '165911', '166207', '166450', '193824', '223521', '243530']
nosy_count = 4.0
nosy_names = ['ncoghlan', 'chris.jerdonek', 'eric.snow', 'bobcatfish']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue15376'
versions = ['Python 3.5']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100