singledispatch does not work with positional arguments with default values.
Open
Nobody has claimed this yet.
3.10
3.9 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 47030 |
|---|---|
| Nosy | @akulakov, @randolf-scholz |
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 2022-03-15.18:46:49.092>
labels = ['type-feature', '3.9', '3.10']
title = 'singledispatch does not work with positional arguments with default values.'
updated_at = <Date 2022-03-22.03:50:00.049>
user = 'https://github.com/randolf-scholz'
bugs.python.org fields:
activity = <Date 2022-03-22.03:50:00.049>
actor = 'andrei.avk'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2022-03-15.18:46:49.092>
creator = 'randolf.scholz'
dependencies = []
files = []
hgrepos = []
issue_num = 47030
keywords = []
message_count = 2.0
messages = ['415274', '415740']
nosy_count = 2.0
nosy_names = ['andrei.avk', 'randolf.scholz']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue47030'
versions = ['Python 3.9', '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 at the singledispatch entry point and reproduce the reported behavior with positional arguments that have default values. Determine the expected dispatch behavior and verify that such calls dispatch correctly, including regression coverage for the reported case.
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
- Needs clarification
- Newbie friendliness
- 28/100