[subinterpreters] Improve test coverage for subinterpreters

Open
#68,741 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

The issue mentions subinterpreters and the Tests component but names no files or tests. Start by locating the existing subinterpreter tests and determine which behavior lacks coverage; done means adding focused coverage and verifying the relevant test suite.

Written by the indexing model from the issue text.

Description

tests topic-subinterpreters
BPO 24553
Nosy @ncoghlan, @encukou, @skrah, @ericsnowcurrently

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 2015-07-03.00:30:03.577>
labels = ['expert-subinterpreters', 'tests']
title = '[subinterpreters] Improve test coverage for subinterpreters'
updated_at = <Date 2020-05-15.00:41:59.313>
user = 'https://github.com/ericsnowcurrently'

bugs.python.org fields:

activity = <Date 2020-05-15.00:41:59.313>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests', 'Subinterpreters']
creation = <Date 2015-07-03.00:30:03.577>
creator = 'eric.snow'
dependencies = []
files = []
hgrepos = []
issue_num = 24553
keywords = []
message_count = 14.0
messages = ['246107', '246149', '246207', '246208', '246237', '246238', '246253', '246255', '246256', '246257', '246298', '246677', '246695', '319559']
nosy_count = 5.0
nosy_names = ['ncoghlan', 'grahamd', 'petr.viktorin', 'skrah', 'eric.snow']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue24553'
versions = ['Python 3.5', 'Python 3.6']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.