python / python/cpython

Consider enabling -Wmissing-prototypes

Open
#79,439 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.8 (EOL) build type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 35258
Nosy @vstinner, @ericsnowcurrently, @izbyshev

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-11-15.17:33:43.181>
labels = ['type-feature', '3.8', 'build']
title = 'Consider enabling -Wmissing-prototypes'
updated_at = <Date 2019-02-01.19:39:03.909>
user = 'https://github.com/izbyshev'

bugs.python.org fields:

activity = <Date 2019-02-01.19:39:03.909>
actor = 'eric.snow'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2018-11-15.17:33:43.181>
creator = 'izbyshev'
dependencies = []
files = []
hgrepos = []
issue_num = 35258
keywords = []
message_count = 1.0
messages = ['329954']
nosy_count = 3.0
nosy_names = ['vstinner', 'eric.snow', 'izbyshev']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue35258'
versions = ['Python 3.8']

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 names no files, tests, or build entry points; it only proposes enabling the -Wmissing-prototypes compiler warning for CPython. Start by locating the C build configuration and checking how compiler warnings are configured. Done means the warning is enabled without introducing unresolved diagnostics, with appropriate build validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.