[issue10469] test_socket fails using Visual Studio 2010

Kristján Valur Jónsson added the comment: This has been fixed with the proper 2010 support -- resolution: -> fixed status: open -> closed superseder: -> Support Visual Studio 2010 ___ Python tracker

[issue10469] test_socket fails using Visual Studio 2010

Kristján Valur Jónsson added the comment: Added a patch as used by CCP in production. Covers more WSA cases. -- nosy: +krisvale Added file: http://bugs.python.org/file24985/cpython_75849_to_75851.diff ___ Python tracker

[issue10469] test_socket fails using Visual Studio 2010

Brian Curtin added the comment: FYI: this would likely be handled through #13210. I have a conversion sandbox started at http://hg.python.org/sandbox/vs2010port/ and am working through fixing test failures after the initial conversion. -- ___ Pytho

[issue10469] test_socket fails using Visual Studio 2010

Sébastien Sablé added the comment: I can also confirm that this patch corrects the problem with test_asyncore for Python 2.7 built with VS2010. -- nosy: +sable ___ Python tracker _

[issue10469] test_socket fails using Visual Studio 2010

Simon Buchan added the comment: Confirming this patch fixes the test_aynsc* tests in my VS10 build. Shouldn't it swap all WSA* defines to protect against this in the future, though? Alternatively, should the check for WSA* codes existing be in Lib\asyncore.py? -- nosy: +Simon ___

[issue10469] test_socket fails using Visual Studio 2010

Changes by Daniel Albeseder : -- title: test_socket fails -> test_socket fails using Visual Studio 2010 ___ Python tracker ___ ___ Pyt

[issue10469] test_socket fails

Daniel Albeseder added the comment: Ok I did switched the preference for all "new" defines inside VC++ errno.h to use the WSA* alternatives if available. Now test_socket passes for me, and the test_asyncore which did block before, now passes without a problem. -- Added file: http://b

[issue10469] test_socket fails

Martin v. Löwis added the comment: > Only in the "system_error" file. > (http://msdn.microsoft.com/en-us/library/ee372194.aspx) > Seem to be a C++0X standard header file. (I assume you have actually scanned the crt\src folder as well) Then it's indeed safe to ignore. > http://msdn.microsoft

[issue10469] test_socket fails

Daniel Albeseder added the comment: Only in the "system_error" file. (http://msdn.microsoft.com/en-us/library/ee372194.aspx) Seem to be a C++0X standard header file. http://msdn.microsoft.com/en-us/library/5814770t.aspx talks about the Posix codes only for compatibility reasons. --

[issue10469] test_socket fails

Martin v. Löwis added the comment: Oops, I was confused. My copy is VS 2008, of course. So that's another incompatible change in VS 2010. Tcl, Ruby, and curl are ahead of us, here: http://redmine.ruby-lang.org/issues/show/3092 http://sourceforge.net/tracker/index.php?func=detail&aid=3019634&gr

[issue10469] test_socket fails

Daniel Albeseder added the comment: c:\Program Files\Microsoft Visual Studio 10.0\VC\include\errno.h The content of my errno.h: ... #define EILSEQ 42 #define STRUNCATE 80 #endif #endif /* Support EDEADLOCK for compatibility with older MS-C versions */ #define EDEADLOCK ED

[issue10469] test_socket fails

Martin v. Löwis added the comment: OK, so what's the path to errno.h? In the errno.h included in my copy of VS 2010, the errno values only go up to 42 (80 if you count STRUNCATE), and EWOULDBLOCK is not defined in this header file. -- ___ Python tr

[issue10469] test_socket fails

Daniel Albeseder added the comment: #define EWOULDBLOCK 140 #define WSAEWOULDBLOCK 10035L The editor suggests that EWOULDBLOCK is already defined, therefore its code is used, i.e. 140. #define ECONNREFUSED107 #define WSAECONNREFUSED 10061L The E* ar

[issue10469] test_socket fails

Martin v. Löwis added the comment: Kotan: please perform the following procedure: 1. Open pcbuild.sln 2. In the pythoncore project, open errnomodule.c 3. find the reference to EWOULDBLOCK and WSAEWOULDBLOCK 4. for each one, "go to definition" 5. report here what header files Visual Studio think

[issue10469] test_socket fails

Brian Curtin added the comment: Daniel: If you need VS2008, you can get it here: http://www.microsoft.com/express/Downloads/#2008-Visual-CPP -- ___ Python tracker ___ _

[issue10469] test_socket fails

Daniel Albeseder added the comment: As this was requested on IRC, I put the Visual C++ 2010 Express solution and project files here as well. The patch "pcbuild_vs2010.patch" should be applied to the PCbuild directory. -- keywords: +patch Added file: http://bugs.python.org/file19686/pc

[issue10469] test_socket fails

Changes by Antoine Pitrou : -- nosy: +amaury.forgeotdarc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue10469] test_socket fails

Antoine Pitrou added the comment: The core problem seems to be that the errno module has mismatching values on your Python build (for ECONNREFUSED and EWOULDBLOCK, at least, which explains all 4 failures). On a Windows 7 VM here: >>> errno.ECONNREFUSED 10061 >>> errno.EWOULDBLOCK 10035 -

[issue10469] test_socket fails

Changes by Antoine Pitrou : -- nosy: +brian.curtin, loewis, tim.golden ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue10469] test_socket fails

Daniel Albeseder added the comment: current revision = svn revision 86553 -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue10469] test_socket fails

New submission from Daniel Albeseder : Using WinXP I compiled python 3.2 from the current sources using Visual C++ 2010 Express. Running rt -v test_socket resulted in the attached output. The tests testSmallReadNonBlocking and testWriteNonBlocking have errors, and an assertion fails for tes