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.

Author serhiy.storchaka
Recipients Alexander Riccio, loewis, paul.moore, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2015-12-17.12:14:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thank you Alexander for your work. I agree that we have to use maximal warning level available in the compiler, and specially disable those warning categories that produces mainly false positives with CPython sources. See also similar issue23545 about GCC.

And of course I concur with Martin that we have first fix all non-false warnings before increase warning level (as we have done for GCC), and it would be better to do this in separate issues.
Date User Action Args
2015-12-17 12:14:55serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, paul.moore, tim.golden, zach.ware, steve.dower, Alexander Riccio
2015-12-17 12:14:55serhiy.storchakasetmessageid: <>
2015-12-17 12:14:55serhiy.storchakalinkissue25878 messages
2015-12-17 12:14:55serhiy.storchakacreate