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 terry.reedy
Recipients Alexander Riccio, BreamoreBoy, christian.heimes, loewis, paul.moore, r.david.murray, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2016-08-24.18:44:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472064244.75.0.905559522222.issue25847@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2016-08-24 18:44:04terry.reedysetrecipients: + terry.reedy, loewis, paul.moore, christian.heimes, tim.golden, r.david.murray, BreamoreBoy, zach.ware, steve.dower, Alexander Riccio
2016-08-24 18:44:04terry.reedysetmessageid: <1472064244.75.0.905559522222.issue25847@psf.upfronthosting.co.za>
2016-08-24 18:44:04terry.reedylinkissue25847 messages
2016-08-24 18:44:04terry.reedycreate