Allow easy display of local variables in log messages?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- observability
Research direction
Start by reading PR #29299 and the discussion for bpo-23597, then review dependency bpo-22936 about showing locals in tracebacks. No files or tests are named; the work is done only once the intended behavior for displaying local variables in log messages is agreed and implemented.
Written by the indexing model from the issue text.
Description
| BPO | 23597 |
|---|---|
| Nosy | @ncoghlan, @rbtcollins, @iritkatriel, @moi90 |
| PRs | |
| Dependencies |
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-03-06.02:12:46.169>
labels = ['type-feature', '3.11']
title = 'Allow easy display of local variables in log messages?'
updated_at = <Date 2021-10-29.06:27:23.466>
user = 'https://github.com/ncoghlan'
bugs.python.org fields:
activity = <Date 2021-10-29.06:27:23.466>
actor = 'moi90'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2015-03-06.02:12:46.169>
creator = 'ncoghlan'
dependencies = ['22936']
files = []
hgrepos = []
issue_num = 23597
keywords = ['patch']
message_count = 4.0
messages = ['237319', '237323', '404737', '405287']
nosy_count = 5.0
nosy_names = ['ncoghlan', 'rbcollins', 'cvrebert', 'iritkatriel', 'moi90']
pr_nums = ['29299']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue23597'
versions = ['Python 3.11']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100