Context of documentation for conditional expressions

Open
#65,058 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files or tests. Start by reviewing linked PR gh-119171 and the original BPO issue 20859; completion would require resolving the documented context problem, but the issue does not specify the expected wording or location.

Written by the indexing model from the issue text.

Description

3.11 3.12 3.13 docs easy type-bug
BPO 20859
Nosy @rhettinger, @terryjreedy, @ezio-melotti, @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 2014-03-06.18:48:00.756>
labels = ['type-bug', '3.9', '3.10', '3.11']
title = 'Context of documentation for conditional expressions'
updated_at = <Date 2021-06-23.11:04:06.628>
user = 'https://github.com/terryjreedy'

bugs.python.org fields:

activity = <Date 2021-06-23.11:04:06.628>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2014-03-06.18:48:00.756>
creator = 'terry.reedy'
dependencies = []
files = []
hgrepos = []
issue_num = 20859
keywords = []
message_count = 2.0
messages = ['212835', '396409']
nosy_count = 4.0
nosy_names = ['rhettinger', 'terry.reedy', 'ezio.melotti', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20859'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

Linked PRs
  • gh-119171
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.