[issue5407] Broken Py3.1 release build in Visual Studio 2005

Changes by Terry J. Reedy : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Hirokazu Yamamoto added the comment: OK, sorry for interruption. ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Kristján Valur Jónsson added the comment: no, r69560/r69793 also removed the call to _set_invalid_parameter_handler(). The default parameter handling is now left alone in the crt which will throw up a dialogue box both in the release and debug versions. Anyway, the issue (strange block layo

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Raymond Hettinger added the comment: For me, it was the release builds that were failing. With the fix just added, all is well now. ___ Python tracker ___ ___

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Hirokazu Yamamoto added the comment: Sorry for interruption. Maybe is this CRT internal hack needed for debug build only? I believe _ASSERTE is only enabled for debug build. ___ Python tracker __

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Raymond Hettinger added the comment: The fix works for me. It all builds once again :-) ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Kristján Valur Jónsson added the comment: Okay, I have submitted revision 70119 that fixes this. This is most weird, though. It is as though the non-_DEBUG crt doesn't match the headers supplied with the CRT sources that come with visual studio 2005. One possible reason is that there is some

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Kristján Valur Jónsson added the comment: I didn't know that VS2005 was supported. We jumped from 2003 to 2008, didn't we? Anyway, I'll fix this, we can't have things crashing. ___ Python tracker

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Changes by Antoine Pitrou : -- assignee: pitrou -> krisvale ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Changes by Antoine Pitrou : -- nosy: +ocean-city ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Changes by Antoine Pitrou : -- nosy: +krisvale ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue5407] Broken Py3.1 release build in Visual Studio 2005

Antoine Pitrou added the comment: I can't reproduce under Visual Studio Express 2008, release mode. I suspect it may be due to r69560/r69793 (introduction of a Windows-specific function named _PyVerify_fd()). ___ Python tracker

[issue5407] Broken Py3.1 release build in Visual Studio 2005

New submission from Raymond Hettinger : The build crashes and it seems related to io.py. This started about two weeks ago. Before that, it built fine. -- Build started: Project: _ssl, Configuration: Release Win32 -- Performing Pre-Build Event... Traceback (most recent call last): Fi