C API dictionary views type checkers are not documented

Open
#80,008 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, python
Domain
api, documentation

Research direction

Start by locating the CPython documentation for C API dictionary views and compare the available type-checker functions with their documented entries. The issue names no files or tests; done means the relevant dictionary-view type checkers are documented consistently with the other C API functions.

Written by the indexing model from the issue text.

Description

docs topic-C-API type-feature
BPO 35827
Nosy @salty-horse, @tiran, @serhiy-storchaka

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 2019-01-25.12:05:04.644>
labels = ['3.7', '3.8', '3.9', 'expert-C-API', 'type-feature', 'docs']
title = 'C API dictionary views type checkers are not documented'
updated_at = <Date 2019-12-10.11:21:51.844>
user = 'https://github.com/salty-horse'

bugs.python.org fields:

activity = <Date 2019-12-10.11:21:51.844>
actor = 'serhiy.storchaka'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'C API']
creation = <Date 2019-01-25.12:05:04.644>
creator = 'salty-horse'
dependencies = []
files = []
hgrepos = []
issue_num = 35827
keywords = []
message_count = 2.0
messages = ['334355', '358182']
nosy_count = 4.0
nosy_names = ['salty-horse', 'christian.heimes', 'docs@python', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue35827'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9']

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.