[issue9784] _msi.c warnings under 64-bit Windows

Martin v. Löwis report at bugs.python.org
Sat Sep 25 08:36:00 CEST 2010

Martin v. Löwis <martin at v.loewis.de> added the comment:

> Martin Lowis do you mean API when you type SDK?

When I said "SDK examples", then I really meant "examples as published
in the SDK", not "examples as published in the API" (and the SDK
documentation, in turn, is published on msdn).
But yes, the SDK examples use Win32 directly.

> If I understand what you are saying, you would rather use the Win32
> API instead of the CRT API?


> It may interest you to know that _open calls CreateFile internally,
> _read calls ReadFile, _write calls WriteFile, _lseek calls
> SetFilePointer, and _close calls CloseHandle. 

I'm fully aware of that.

> We could rewrite the functions using the Win32 API directly but we
> don’t have to.  I realize this is a Windows only module but the use
> of the CRT API is more familiar to a majority of the Python
> developers (I would guess).

I have the long-term plan to eliminate all CRT usage from Python
on Windows. In this case, there is a straight-forward opportunity
to do so. Nothing is really gained from using the CRT (as the cabinet
SDK is probably even less familiar to Python developers than
CreateFile), plus using the CRT causes compiler warnings, as
Microsoft clearly intends that these routines would be implemented
using the Windows API directly.


Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list