python / python/cpython

Fix documentation for __instancecheck__

Open
#79,264 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.8 (EOL) docs type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 35083
Nosy @JulienPalard, @tirkarthi, @Rhodolite, @cdonovick, @eirrgang

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 2018-10-27.20:14:41.592>
labels = ['type-feature', '3.8', 'docs']
title = 'Fix documentation for __instancecheck__'
updated_at = <Date 2020-12-15.13:52:24.473>
user = 'https://github.com/Rhodolite'

bugs.python.org fields:

activity = <Date 2020-12-15.13:52:24.473>
actor = 'eirrgang'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2018-10-27.20:14:41.592>
creator = 'joydiamond'
dependencies = []
files = []
hgrepos = []
issue_num = 35083
keywords = []
message_count = 5.0
messages = ['328658', '328687', '330286', '383046', '383057']
nosy_count = 6.0
nosy_names = ['docs@python', 'mdk', 'xtreak', 'joydiamond', 'donovick', 'eirrgang']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue35083'
versions = ['Python 2.7', 'Python 3.8']

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.

Research direction

Search the Python documentation for instancecheck and read the linked BPO 35083 discussion to determine which wording is inaccurate or missing. Done means the relevant documentation reflects the intended behavior and the documentation checks pass; no specific file or test is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.