python / python/cpython

"expression" is erroneous in the doc

Open
#89,810 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.10 3.11 3.9 (EOL) docs
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 45647
Nosy @Arthur-Milchior

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 2021-10-28.14:51:26.855>
labels = ['3.11', '3.9', '3.10', 'docs']
title = '"expression" is erroneous in the doc'
updated_at = <Date 2021-11-02.16:23:39.061>
user = 'https://github.com/Arthur-Milchior'

bugs.python.org fields:

activity = <Date 2021-11-02.16:23:39.061>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2021-10-28.14:51:26.855>
creator = 'Arthur-Milchior'
dependencies = []
files = []
hgrepos = []
issue_num = 45647
keywords = []
message_count = 1.0
messages = ['405189']
nosy_count = 2.0
nosy_names = ['docs@python', 'Arthur-Milchior']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue45647'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

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

No file or test is identified in the issue. Start by reviewing the linked BPO issue 45647 and locating the documentation passage described there; the work is done when the erroneous use of “expression” is corrected and the relevant documentation checks pass.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.