dir(<bound method>) should include dunder attributes of the unbound method
Open
Nobody has claimed this yet.
3.7 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29117 |
|---|---|
| Nosy | @terryjreedy, @anntzer, @zhangyangyu |
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-12-30.21:51:10.086>
labels = ['interpreter-core', 'type-bug', '3.7']
title = 'dir(<bound method>) should include dunder attributes of the unbound method'
updated_at = <Date 2017-01-06.21:51:15.327>
user = 'https://github.com/anntzer'
bugs.python.org fields:
activity = <Date 2017-01-06.21:51:15.327>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2016-12-30.21:51:10.086>
creator = 'Antony.Lee'
dependencies = []
files = []
hgrepos = []
issue_num = 29117
keywords = []
message_count = 2.0
messages = ['284347', '284859']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'Antony.Lee', 'xiang.zhang']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29117'
versions = ['Python 3.6', 'Python 3.7']
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 reproducing the reported difference between dir() on a bound method and its unbound method, then locate the interpreter-core implementation and relevant tests. Add coverage for the expected dunder attributes and confirm that the bound-method result includes those from the unbound method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100