[issue25847] CPython not using Visual Studio code analysis!

[Terry J. Reedy]

Terry J. Reedy added the comment:

Like Mark, I have noticed that there are enough ignored VS warnings now to not think we need more.

Every time socketmodule is recompiled, for instance, I see all the scary deprecation warnings.  These are Windows-specific.  Should the code be changed or should the warnings be silenced with  _WINSOCK_DEPRECATED_NO_WARNINGS, as suggested?

Other warnings appear to come from code compiled on all systems.  I presume such code is usually developed on Linux.  Is such code compiling warning free on gcc?  Are there conflicting demands and opinions from gcc and vs?

I am a little confused on the actual policy for compiling on Windows.  I believe Victor Stinner has done some patches to stop them, but...
(Steve)> Doing the work to clean up the warnings really has to come second, ultimately.
Second to what?

Should I just close my eyes when running build.bat?

----------
nosy: +terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue25847>
_______________________________________