borgbackup/borg

can we reasonably enable more warnings?

Open

#9140 opened on Nov 3, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (10,086 stars) (732 forks)batch import
help wantedsecurity

Description

One nice to have item from https://www.bestpractices.dev/en/projects/271 (warnings_strict) would be to enable more warnings.

What can we do on the Python, Cython, C level?

Contributor guide

Tech stack
pythonc
Domain
build systemdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with build systemKnowledge of compiler warnings
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.