[doc] Unintuitive error when using generator expression in class property
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
docs
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 26951 |
|---|---|
| Nosy | @mdickinson, @stevendaprano, @serhiy-storchaka, @frewsxcv, @zhangyangyu, @Vgr255 |
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-05-04.14:34:32.938>
labels = ['3.11', 'type-bug', '3.9', '3.10', 'docs']
title = '[doc] Unintuitive error when using generator expression in class property'
updated_at = <Date 2021-12-12.00:51:42.440>
user = 'https://github.com/frewsxcv'
bugs.python.org fields:
activity = <Date 2021-12-12.00:51:42.440>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2016-05-04.14:34:32.938>
creator = 'corey'
dependencies = []
files = []
hgrepos = []
issue_num = 26951
keywords = []
message_count = 5.0
messages = ['264819', '264821', '264830', '264845', '348191']
nosy_count = 7.0
nosy_names = ['mark.dickinson', 'steven.daprano', 'docs@python', 'serhiy.storchaka', 'corey', 'xiang.zhang', 'abarry']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26951'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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 by reading the linked BPO issue 26951 and the surrounding Python documentation for generator expressions and class properties. Identify the documentation location and intended explanation from the historical discussion; done means the unintuitive error and its cause are explained clearly in the relevant documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100