can we reasonably enable more warnings?

描述

貢獻者指南

技術棧

pythonc

領域

build systemdeveloper experience

議題類型

feature

難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。

3

預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。

half day

活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。

fresh

清晰度議題是否清楚說明預期改動、驗收標準和下一步。

mostly clear

前置要求

Familiarity with build systemKnowledge of compiler warnings

新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。

35

研究方向

Investigate the current build scripts (setup.py, Makefile, etc.) to see which warnings are already enabled at the Python, Cython, and C levels. Review the bestpractices.dev criteria for warnings strict and propose additional compiler flags or Python warnings that can be enabled without introducing noise. Check for any existing CI configuration that might need modification. Suggest specific flags like Wall Wextra for C or Werror for Python warnings, and verify they don't break the build.