Explain in the "Data Model" document why arguments to __init__ are ok when __new__ is not defined
Open
Nobody has claimed this yet.
docs
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 28672 |
|---|---|
| Nosy | @jsbueno |
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 2016-11-12.05:50:12.182>
labels = ['type-feature', 'docs']
title = 'Explain in the "Data Model" document why arguments to __init__ are ok when __new__ is not defined'
updated_at = <Date 2016-11-12.05:50:12.182>
user = 'https://github.com/jsbueno'
bugs.python.org fields:
activity = <Date 2016-11-12.05:50:12.182>
actor = 'jsbueno'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2016-11-12.05:50:12.182>
creator = 'jsbueno'
dependencies = []
files = []
hgrepos = []
issue_num = 28672
keywords = []
message_count = 1.0
messages = ['280633']
nosy_count = 2.0
nosy_names = ['jsbueno', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue28672'
versions = ['Python 3.6']
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
Open Python's "Data Model" document and locate the explanation of object construction involving new and init. Clarify why arguments can still be passed to init when new is not defined, using the surrounding text for context. Done means the document explains this behavior clearly; no test or specific file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100