Valgrind documentation seems to need updating

Open
#76,847 5 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
python
Domain
documentation

Research direction

The issue identifies Valgrind documentation as needing an update but names no documentation file, test, or specific change. Start by locating the existing Valgrind guidance in the Python documentation and reviewing the linked historical issue details. Done means the outdated guidance and its required scope are identified and the relevant documentation is updated.

Written by the indexing model from the issue text.

Description

docs performance
BPO 32666
Nosy @brettcannon, @terryjreedy, @vstinner, @tiran

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-01-25.13:29:45.209>
labels = ['3.8', 'docs']
title = 'Valgrind documentation seems to need updating'
updated_at = <Date 2018-11-03.07:07:33.806>
user = 'https://bugs.python.org/rrt'

bugs.python.org fields:

activity = <Date 2018-11-03.07:07:33.806>
actor = 'rrt'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2018-01-25.13:29:45.209>
creator = 'rrt'
dependencies = []
files = []
hgrepos = []
issue_num = 32666
keywords = []
message_count = 5.0
messages = ['310673', '310842', '310878', '329168', '329188']
nosy_count = 6.0
nosy_names = ['brett.cannon', 'terry.reedy', 'vstinner', 'christian.heimes', 'docs@python', 'rrt']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue32666'
versions = ['Python 3.8']

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.