Add glossary entries to clarify the true/True and false/False distinction

Open
#91,039 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Locate the glossary source in the CPython documentation and review the existing entries for true, True, false, and False. Add glossary entries that explain their distinction, then check the surrounding glossary formatting and documentation build or review process to confirm the entries render correctly.

Written by the indexing model from the issue text.

Description

docs type-feature
BPO 46883
Nosy @stevendaprano

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-02-28.15:18:18.857>
labels = ['3.7', '3.8', '3.9', '3.10', '3.11', 'type-feature', 'docs']
title = 'Add glossary entries to clarify the true/True and false/False distinction'
updated_at = <Date 2022-02-28.15:29:38.351>
user = 'https://github.com/stevendaprano'

bugs.python.org fields:

activity = <Date 2022-02-28.15:29:38.351>
actor = 'steven.daprano'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2022-02-28.15:18:18.857>
creator = 'steven.daprano'
dependencies = []
files = []
hgrepos = []
issue_num = 46883
keywords = []
message_count = 2.0
messages = ['414204', '414206']
nosy_count = 2.0
nosy_names = ['steven.daprano', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46883'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10', '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.