python / python/cpython

Wave documentation doesn't mention signed/unsigned requirements

Open
#86,799 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.10 docs type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 42633
Nosy @terryjreedy

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 2020-12-14.07:03:20.776>
labels = ['type-feature', '3.10', 'docs']
title = "Wave documentation doesn't mention signed/unsigned requirements"
updated_at = <Date 2020-12-18.23:45:56.507>
user = 'https://bugs.python.org/mattgwwalker'

bugs.python.org fields:

activity = <Date 2020-12-18.23:45:56.507>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2020-12-14.07:03:20.776>
creator = 'mattgwwalker'
dependencies = []
files = []
hgrepos = []
issue_num = 42633
keywords = []
message_count = 2.0
messages = ['382957', '383332']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'docs@python', 'mattgwwalker']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue42633'
versions = ['Python 3.10']

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

The issue does not name a documentation file or test. Start by locating the documentation for Python's wave module and identify where format requirements are described. Done means the relevant documentation clearly states the signed/unsigned requirements.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.