test_runpy causes running all Python tests when run directly

Open
#75,221 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Start with the test_runpy test entry point and review linked PR gh-155256, which indicates that work is already underway. Reproduce how running test_runpy directly discovers tests, then verify that it no longer runs all Python tests when invoked directly.

Written by the indexing model from the issue text.

Description

tests type-bug
BPO 31038
Nosy @brettcannon, @ncoghlan, @vstinner, @ericsnowcurrently, @serhiy-storchaka, @iritkatriel

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 2017-07-25.16:17:29.593>
labels = ['type-bug', 'tests', '3.9', '3.10', '3.11']
title = 'test_runpy causes running all Python tests when run directly'
updated_at = <Date 2022-01-16.18:38:48.803>
user = 'https://github.com/serhiy-storchaka'

bugs.python.org fields:

activity = <Date 2022-01-16.18:38:48.803>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2017-07-25.16:17:29.593>
creator = 'serhiy.storchaka'
dependencies = []
files = []
hgrepos = []
issue_num = 31038
keywords = []
message_count = 4.0
messages = ['299118', '299119', '299236', '410710']
nosy_count = 6.0
nosy_names = ['brett.cannon', 'ncoghlan', 'vstinner', 'eric.snow', 'serhiy.storchaka', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue31038'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

Linked PRs
  • gh-155256
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.