[issue26411] Suggestion concerning compile-time warnings

2016-02-22 Thread Brett Cannon
Changes by Brett Cannon : -- resolution: -> not a bug status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue26411] Suggestion concerning compile-time warnings

2016-02-22 Thread Brett Cannon
Brett Cannon added the comment: 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 wa

[issue26411] Suggestion concerning compile-time warnings

2016-02-22 Thread SilentGhost
Changes by SilentGhost : -- nosy: +benjamin.peterson, brett.cannon, georg.brandl, ncoghlan, yselivanov ___ Python tracker ___ ___ Pyth

[issue26411] Suggestion concerning compile-time warnings

2016-02-22 Thread Devyn Johnson
New submission from Devyn Johnson: 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 understa