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 loewis
Recipients giampaolo.rodola, jafo, jaraco, lemburg, loewis, nnorwitz, swarren
Date 2009-05-22.19:58:09
SpamBayes Score 1.134943e-05
Marked as misclassified No
Message-id <4A1703CE.7010206@v.loewis.de>
In-reply-to <1242966100.94.0.996788852311.issue1578269@psf.upfronthosting.co.za>
Content
> The first warning might be a problem.  I understand from the docs
> (http://msdn.microsoft.com/en-us/library/aa363866.aspx) that all I need
> to do is include windows.h, which is already included... but still the
> function prototype isn't present.  This might be because a preprocessor
> declaration of WINVER isn't set high enough... but since the same
> executable is built for all versions of Windows, how is this reconciled
> in the compiler?

Good point. Unfortunately, backwards compatibility requires this to
be hackish. We currently strive for compatibility with Windows 2000,
so we cannot statically reference these functions (unless we increase
the minimum required Windows version - but we surely have to support XP
for many years to come).

So, in essence, you need to GetProcAddress. See other examples in
posixmodule.c for how this is done, and raise an exception
(NotImplementedError? WindowsError with ERROR_CALL_NOT_IMPLEMENTED
?) if you can't find the function.
History
Date User Action Args
2009-05-22 19:58:12loewissetrecipients: + loewis, lemburg, nnorwitz, jafo, jaraco, giampaolo.rodola, swarren
2009-05-22 19:58:10loewislinkissue1578269 messages
2009-05-22 19:58:09loewiscreate