[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

Kristján Valur Jónsson added the comment: Closing this defect, as the issues seems worked around on our end. Btw, here is the issue on Microsoft's end. They've marked it as "won't fix". https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx? FeedbackID=409955&wa=wsignin1.0 ---

[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

Martin v. Löwis added the comment: Why is this still open? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

Benjamin Peterson added the comment: Could someone port this to 3.1, please? I'm not Windows savy enough to do it. -- nosy: +benjamin.peterson ___ Python tracker ___

[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

Amaury Forgeot d'Arc added the comment: Sorry, but for the moment the only internet access I have is behind a firewall and I cannot use SVN. Could you do it instead? -- ___ Python tracker __

[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

Amaury Forgeot d'Arc added the comment: Oops, that's right. This second patch removes the check with _get_osfhandle(). It was not really necessary: when the trick does not work, python will tell it loudly enough. -- Added file: http://bugs.python.org/file13542/verify_fd-2.patch __

[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

Amaury Forgeot d'Arc added the comment: I found a correction using the _msize() function, which returns the size of a malloc'ed block. It is used to compute sizeof(ioinfo) at runtime. The exact definition of the structure is no longer important; only the first two fields are needed, which is a

[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

Amaury Forgeot d'Arc added the comment: The problem with Windows 2000 is that it is not enough to distribute the CRT. For example, I am sure that a few months ago the version ending with .1433 was not present on my machine; the version in the system32 directory was .762 (the one shipped with

[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

Martin v. Löwis added the comment: > We could also simply redistribute the MSVCRT in python/bin, as we are > allowed to. We *do* distribute the CRT with Python, and it works just fine. The report is about VS 2005 -- title: test_fdopen fails with vs2005, release build on Windows 2000 -

[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

Changes by Amaury Forgeot d'Arc : -- nosy: +krisvale ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue5623] test_fdopen fails with vs2005, release build on Windows 2000

New submission from Amaury Forgeot d'Arc : Python trunk, compiled with VS2005 SP1, release build on Windows 2000: >>> import os >>> fd = os.open("t", 0) >>> os.close(fd) Traceback (most recent call last): File "", line 1, in OSError: [Errno 9] Bad file descriptor The _PyVerify_fd() returned F