Output closing parenthesis in ast.dump() on separate line
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start at the ast.dump() entry point and review the existing python/cpython#19039 pull request, which is referenced in the issue. Confirm that the closing parenthesis is emitted on a separate line and use the pull request's tests or examples to verify the expected output.
Written by the indexing model from the issue text.
Description
| BPO | 39989 |
|---|---|
| Nosy | @rhettinger, @terryjreedy, @mdickinson, @ericvsmith, @benjaminp, @serhiy-storchaka, @asottile, @pablogsal |
| PRs |
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 2020-03-17.08:06:12.199>
labels = ['type-feature', 'library', '3.9']
title = 'Output closing parenthesis in ast.dump() on separate line'
updated_at = <Date 2020-03-22.21:07:55.789>
user = 'https://github.com/serhiy-storchaka'
bugs.python.org fields:
activity = <Date 2020-03-22.21:07:55.789>
actor = 'Anthony Sottile'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-03-17.08:06:12.199>
creator = 'serhiy.storchaka'
dependencies = []
files = []
hgrepos = []
issue_num = 39989
keywords = ['patch']
message_count = 6.0
messages = ['364391', '364411', '364426', '364427', '364457', '364824']
nosy_count = 8.0
nosy_names = ['rhettinger', 'terry.reedy', 'mark.dickinson', 'eric.smith', 'benjamin.peterson', 'serhiy.storchaka', 'Anthony Sottile', 'pablogsal']
pr_nums = ['19039']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue39989'
versions = ['Python 3.9']
- 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