Documenting dataclass and namedtuple changes for structural pattern matching
Open
Nobody has claimed this yet.
docs
topic-dataclasses
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43761 |
|---|---|
| Nosy | @gvanrossum, @rhettinger, @ericvsmith, @brandtbucher, @freundTech |
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-04-07.10:40:27.457>
labels = ['3.10', 'docs']
title = 'Documenting dataclass and namedtuple changes for structural pattern matching'
updated_at = <Date 2021-04-12.16:35:21.092>
user = 'https://github.com/freundTech'
bugs.python.org fields:
activity = <Date 2021-04-12.16:35:21.092>
actor = 'brandtbucher'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2021-04-07.10:40:27.457>
creator = 'freundTech'
dependencies = []
files = []
hgrepos = []
issue_num = 43761
keywords = []
message_count = 12.0
messages = ['390413', '390426', '390430', '390457', '390676', '390679', '390685', '390692', '390707', '390725', '390733', '390865']
nosy_count = 6.0
nosy_names = ['gvanrossum', 'rhettinger', 'eric.smith', 'docs@python', 'brandtbucher', 'freundTech']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue43761'
versions = ['Python 3.10']
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 43761 and the existing documentation for structural pattern matching, dataclasses, and namedtuples. Identify where the Python 3.10 changes need explanation, then update the relevant documentation and confirm that it clearly describes the supported changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100