syntactic sugar: type coercion on pointer assignment

Open
#49,399 5 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

No source files, tests, or entry points are named. Start by locating the ctypes pointer-assignment behavior and reviewing the historical BPO issue; the work is done when the coercion syntax and supported behavior are clearly specified and covered by tests.

Written by the indexing model from the issue text.

Description

3.10 topic-ctypes type-feature
BPO 5149
Nosy @amauryfa, @abalkin, @meadori

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 2009-02-04.01:20:02.204>
labels = ['ctypes', 'type-feature', '3.10']
title = 'syntactic sugar: type coercion on pointer assignment'
updated_at = <Date 2020-10-25.22:49:47.999>
user = 'https://bugs.python.org/PeterASilva'

bugs.python.org fields:

activity = <Date 2020-10-25.22:49:47.999>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['ctypes']
creation = <Date 2009-02-04.01:20:02.204>
creator = 'PeterASilva'
dependencies = []
files = []
hgrepos = []
issue_num = 5149
keywords = []
message_count = 5.0
messages = ['81123', '141747', '143452', '143657', '143659']
nosy_count = 5.0
nosy_names = ['amaury.forgeotdarc', 'belopolsky', 'PeterASilva', 'meador.inge', 'vladris']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue5149'
versions = ['Python 3.10']

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.