Should we re-export `PyObj_FromPtr` in `ctypes`?

Open
#90,743 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reading the ctypes component context and the linked BPO issue 46585 discussion about PyObj_FromPtr. Determine whether the public ctypes API should re-export it and what compatibility or maintenance implications the discussion identifies; the issue is complete only after that design question has a decided outcome.

Written by the indexing model from the issue text.

Description

3.11 topic-ctypes type-feature
BPO 46585
Nosy @amauryfa, @abalkin, @meadori, @zware, @eryksun, @sobolevn

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-01-30.15:03:49.809>
labels = ['ctypes', 'type-bug', '3.11']
title = 'Should we re-export `PyObj_FromPtr` in `ctypes`?'
updated_at = <Date 2022-01-30.17:14:33.160>
user = 'https://github.com/sobolevn'

bugs.python.org fields:

activity = <Date 2022-01-30.17:14:33.160>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['ctypes']
creation = <Date 2022-01-30.15:03:49.809>
creator = 'sobolevn'
dependencies = []
files = []
hgrepos = []
issue_num = 46585
keywords = []
message_count = 2.0
messages = ['412155', '412165']
nosy_count = 6.0
nosy_names = ['amaury.forgeotdarc', 'belopolsky', 'meador.inge', 'zach.ware', 'eryksun', 'sobolevn']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue46585'
versions = ['Python 3.11']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.