[doc] Document that __getattr__ can be called before __init__ (e.g. by pickle)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start by locating the Python documentation for getattr and the pickle-related behavior described in the issue. Update the relevant documentation to state that getattr may be called before init, using pickle as an example, then run the applicable documentation checks and verify the rendered wording.
Written by the indexing model from the issue text.
Description
| BPO | 16242 |
|---|---|
| Nosy | @pitrou, @avassalotti |
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-10-15.18:11:13.593>
labels = ['3.11', 'type-feature', 'library', 'docs']
title = '[doc] Document that __getattr__ can be called before __init__ (e.g. by pickle)'
updated_at = <Date 2021-11-26.23:10:29.318>
user = 'https://bugs.python.org/powderflask'
bugs.python.org fields:
activity = <Date 2021-11-26.23:10:29.318>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2012-10-15.18:11:13.593>
creator = 'powderflask'
dependencies = []
files = []
hgrepos = []
issue_num = 16242
keywords = []
message_count = 2.0
messages = ['172993', '223114']
nosy_count = 4.0
nosy_names = ['pitrou', 'alexandre.vassalotti', 'docs@python', 'powderflask']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue16242'
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
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
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