Repository navigation
_warnings settings are process-wide #58027
Description
| BPO | 13819 |
|---|---|
| Nosy | @pitrou, @alex, @nanjekyejoannah |
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-01-18.20:50:16.644>
labels = ['extension-modules', 'interpreter-core', 'type-bug']
title = '_warnings settings are process-wide'
updated_at = <Date 2019-07-18.17:47:39.164>
user = 'https://github.com/pitrou'bugs.python.org fields:
activity = <Date 2019-07-18.17:47:39.164>
actor = 'nanjekyejoannah'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules', 'Interpreter Core']
creation = <Date 2012-01-18.20:50:16.644>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 13819
keywords = []
message_count = 2.0
messages = ['151563', '223359']
nosy_count = 3.0
nosy_names = ['pitrou', 'alex', 'nanjekyejoannah']
pr_nums = []
priority = 'low'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue13819'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5']
Activity
pitrou commentedon Jan 18, 2012
The settings in the C _warnings module are system-wide instead of being interpreter-wide. It seems the latter would be more desireable (and probably more compatible with the Python warnings module).
BreamoreBoy commentedon Jul 17, 2014
Just a gentle reminder.
iritkatriel commentedon Sep 25, 2022
CC @ericsnowcurrently
aisk commentedon Jun 4, 2024
Hi, I see there is another similar issue in #80918, which was already solved by #13159, so I guess this can be closed now?