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 zach.ware
Recipients larry, zach.ware
Date 2014-02-20.21:56:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392933374.17.0.141811860716.issue20707@psf.upfronthosting.co.za>
In-reply-to
Content
PC/pyconfig.h does "#define hypot _hypot", but VS 2010 and above already define a hypot function (implemented by _hypot), which results in a warning if you have warning 4211 enabled (which warning level 4 does) or a recursive definition which results in a crash at runtime, depending on how you use Python.h.  Python itself doesn't suffer from the runtime crash, but Blender does because of Python.

bf413a97f1a9 fixes it by guarding the #define with #if _MSC_VER < 1600.

This one is kind of borderline for RC phase in my mind, so I leave it up to you to decide, Larry.  It is a serious issue for at least Blender and one other extension author.  On the other hand, this issue has been around since 3.3.0 (the first VS 2010-supporting release) and was only reported this January.
History
Date User Action Args
2014-02-20 21:56:14zach.waresetrecipients: + zach.ware, larry
2014-02-20 21:56:14zach.waresetmessageid: <1392933374.17.0.141811860716.issue20707@psf.upfronthosting.co.za>
2014-02-20 21:56:14zach.warelinkissue20707 messages
2014-02-20 21:56:13zach.warecreate