Provide a way for assertLogs to optionally not hide the logging output

Open
#68,540 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing

Research direction

Start by locating the assertLogs implementation and its existing tests in the Python standard library. Read how assertLogs currently captures and suppresses logging, then determine the expected opt-in behavior from the issue discussion. Done means an optional setting preserves logging output while existing capture behavior and tests remain correct.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 24352
Nosy @rbtcollins, @ezio-melotti, @bitdancer, @voidspace, @zware

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-06-01.19:15:30.777>
labels = ['type-feature', 'library']
title = 'Provide a way for assertLogs to optionally not hide the logging output'
updated_at = <Date 2015-08-21.14:38:32.228>
user = 'https://github.com/bitdancer'

bugs.python.org fields:

activity = <Date 2015-08-21.14:38:32.228>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-06-01.19:15:30.777>
creator = 'r.david.murray'
dependencies = []
files = []
hgrepos = []
issue_num = 24352
keywords = []
message_count = 3.0
messages = ['244608', '248931', '248955']
nosy_count = 5.0
nosy_names = ['rbcollins', 'ezio.melotti', 'r.david.murray', 'michael.foord', 'zach.ware']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue24352'
versions = ['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.