PyObject_GetAttrString and tp_getattr do not agree
Open
Nobody has claimed this yet.
topic-C-API
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39620 |
|---|---|
| Nosy | @loewis, @encukou, @serhiy-storchaka, @ammaraskar, @petdance |
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 2020-02-13.03:23:38.855>
labels = ['expert-C-API', 'type-feature']
title = 'PyObject_GetAttrString and tp_getattr do not agree'
updated_at = <Date 2021-06-22.14:42:14.566>
user = 'https://github.com/petdance'
bugs.python.org fields:
activity = <Date 2021-06-22.14:42:14.566>
actor = 'petr.viktorin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['C API']
creation = <Date 2020-02-13.03:23:38.855>
creator = 'petdance'
dependencies = []
files = []
hgrepos = []
issue_num = 39620
keywords = []
message_count = 4.0
messages = ['361929', '361930', '361931', '361936']
nosy_count = 5.0
nosy_names = ['loewis', 'petr.viktorin', 'serhiy.storchaka', 'ammar2', 'petdance']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue39620'
versions = []
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
No implementation files or tests are named. Start by reading the C API implementations and documentation for PyObject_GetAttrString and tp_getattr, then establish the intended matching behavior and add coverage for the discrepancy. Done means the two APIs agree as specified by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100