Make @atexit.register work for functions with arguments
Open
Nobody has claimed this yet.
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46051 |
|---|---|
| Nosy | @terryjreedy, @serhiy-storchaka, @quapka |
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 2021-12-11.17:27:01.699>
labels = ['type-feature']
title = 'Make @atexit.register work for functions with arguments'
updated_at = <Date 2021-12-20.18:27:46.945>
user = 'https://github.com/quapka'
bugs.python.org fields:
activity = <Date 2021-12-20.18:27:46.945>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2021-12-11.17:27:01.699>
creator = 'quapka'
dependencies = []
files = []
hgrepos = []
issue_num = 46051
keywords = []
message_count = 6.0
messages = ['408321', '408403', '408823', '408949', '408968', '408969']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'serhiy.storchaka', 'quapka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46051'
versions = []
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.
Research direction
Start at the Python standard-library atexit.register entry point and review the linked BPO issue and its six-message discussion. Define the supported argument behavior and add focused coverage for decorator and exit-time invocation before considering the issue complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100