expose PyCell_Type in types module

Open
#75,931 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start with the Python types module and inspect how existing interpreter types are exposed there. Trace the corresponding PyCell_Type declaration and look for related tests or module documentation; done means the type is publicly available through the types module and the relevant checks pass.

Written by the indexing model from the issue text.

Description

3.7 (EOL) stdlib type-feature
BPO 31750
Nosy @gvanrossum, @benjaminp, @serhiy-storchaka, @akvadrako

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 2017-10-10.17:46:02.538>
labels = ['3.7', 'type-feature', 'library']
title = 'expose PyCell_Type in types module'
updated_at = <Date 2017-10-10.20:10:36.838>
user = 'https://github.com/akvadrako'

bugs.python.org fields:

activity = <Date 2017-10-10.20:10:36.838>
actor = 'gvanrossum'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-10-10.17:46:02.538>
creator = 'akvadrako'
dependencies = []
files = []
hgrepos = []
issue_num = 31750
keywords = []
message_count = 6.0
messages = ['304062', '304063', '304067', '304069', '304074', '304078']
nosy_count = 4.0
nosy_names = ['gvanrossum', 'benjamin.peterson', 'serhiy.storchaka', 'akvadrako']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31750'
versions = ['Python 3.7']

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.