This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Suggestion concerning compile-time warnings
Type: enhancement Stage:
Components: Interpreter Core Versions: Python 3.6
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: Devyn Johnson, benjamin.peterson, brett.cannon, georg.brandl, ncoghlan, yselivanov
Priority: normal Keywords:

Created on 2016-02-22 15:22 by Devyn Johnson, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg260686 - (view) Author: Devyn Johnson (Devyn Johnson) Date: 2016-02-22 15:22
I understand that compile-time warnings can typically be ignored. However, from my experience with programming (C STD-2011, for instance), "weird bugs", non-easily-replicable bugs, and odd behaviors disappear when warnings like this are fixed. I also understand that it will be time-consuming to fix each and every minor warning.

I have also noticed (in my own coding-projects) that fixing all warnings generated by -Wextra (and the many other warning flags) allows the compiler to more easily apply various optimizations.
msg260693 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2016-02-22 17:50
We happily accept patches that silence compile-time warnings. Unfortunately most of the ones I come across are cross-platform ones like some discrepancy between OS X and Linux on the size of some POSIX header, so they are low priority and annoying to fix in a way that doesn't affect other platforms.
History
Date User Action Args
2022-04-11 14:58:27adminsetgithub: 70599
2016-02-22 17:51:41brett.cannonsetstatus: open -> closed
resolution: not a bug
2016-02-22 17:50:59brett.cannonsetmessages: + msg260693
2016-02-22 17:43:38SilentGhostsetnosy: + brett.cannon, georg.brandl, ncoghlan, benjamin.peterson, yselivanov
2016-02-22 15:22:59Devyn Johnsoncreate