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 polyvertex
Recipients BreamoreBoy, Luke.Dunstan, V.E.O, amaury.forgeotdarc, christian.heimes, eaducac, m_python, mloskot, mont29, pitrou, polyvertex, steve.dower, tim.golden, tim.peters, twasilczyk@spoon, vstinner
Date 2015-03-12.22:12:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426198327.09.0.153191448122.issue17797@psf.upfronthosting.co.za>
In-reply-to
Content
Hi all, a small update to confirm this issue with version 3.5.0a2 embedded in a native C++ GUI application, having everything built with VS2013 SP4.

Same execution flow as described by Mateusz in msg198689.

I've modified Python/pylifecycle.c file according to Tomasz's attached patch.
It just "works for me" and I've just slightly modified the #ifdef line:

#if defined(MS_WINDOWS) && defined(HAVE_FSTAT) && defined(_MSC_VER) && _MSC_VER >= 1700 && _MSC_VER < 2000

It would definitely be nice to have this workaround applied to the 3.5 branch since MS' fix is lost in release cycle. Would it be too intrusive?
History
Date User Action Args
2015-03-12 22:12:07polyvertexsetrecipients: + polyvertex, tim.peters, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, tim.golden, BreamoreBoy, eaducac, mloskot, V.E.O, steve.dower, m_python, mont29, Luke.Dunstan, twasilczyk@spoon
2015-03-12 22:12:07polyvertexsetmessageid: <1426198327.09.0.153191448122.issue17797@psf.upfronthosting.co.za>
2015-03-12 22:12:07polyvertexlinkissue17797 messages
2015-03-12 22:12:06polyvertexcreate