warnings should use a ContextVar to manage filters/registry

[graingert]

BPO	37604
Nosy	@gvanrossum, @graingert

^{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 = <Date 2020-09-16.19:41:24.989>
created_at = <Date 2019-07-16.13:24:57.641>
labels = ['type-bug', 'library']
title = 'warnings should use a ContextVar to manage filters/registry'
updated_at = <Date 2020-09-16.19:41:24.989>
user = 'https://github.com/graingert'

bugs.python.org fields:

activity = <Date 2020-09-16.19:41:24.989>
actor = 'gvanrossum'
assignee = 'none'
closed = True
closed_date = <Date 2020-09-16.19:41:24.989>
closer = 'gvanrossum'
components = ['Library (Lib)']
creation = <Date 2019-07-16.13:24:57.641>
creator = 'graingert'
dependencies = []
files = []
hgrepos = []
issue_num = 37604
keywords = []
message_count = 4.0
messages = ['348015', '348016', '357809', '377016']
nosy_count = 3.0
nosy_names = ['gvanrossum', 'graingert', 'Eric Wieser']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37604'
versions = []

[graingert]

this would allow warnings.catch_warnings to be threadsafe

[graingert]

note that PEP-550 previously mentions catch_warnings as something that would benefit from some sort of Execution Context management

Context managers like decimal contexts, numpy.errstate, and warnings.catch_warnings.

[EricWieser]

A relevant old issue is https://bugs.python.org/issue6647

[gvanrossum]

Closing for lack of activity.