Possible different behaviour of explicit and implicit __dict__ accessing when involving builtin types' __dict__ descriptors
Open
Nobody has claimed this yet.
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27411 |
|---|---|
| Nosy | @rhettinger, @serhiy-storchaka, @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-06-29.09:57:04.232>
labels = ['interpreter-core', 'type-bug']
title = "Possible different behaviour of explicit and implicit __dict__ accessing when involving builtin types' __dict__ descriptors"
updated_at = <Date 2016-09-27.10:13:50.266>
user = 'https://github.com/zhangyangyu'
bugs.python.org fields:
activity = <Date 2016-09-27.10:13:50.266>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2016-06-29.09:57:04.232>
creator = 'xiang.zhang'
dependencies = []
files = []
hgrepos = []
issue_num = 27411
keywords = []
message_count = 2.0
messages = ['269470', '277510']
nosy_count = 3.0
nosy_names = ['rhettinger', 'serhiy.storchaka', 'xiang.zhang']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27411'
versions = ['Python 3.6']
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
The issue names no files, tests, or entry points. Start by reproducing the differing explicit and implicit dict behavior involving builtin type descriptors, then trace the interpreter-core handling that produces it. Done means the behavior is explained and a focused regression test and agreed fix are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100