[python-win32] GetKeyboardState - API not covered?
mhammond at skippinet.com.au
Wed Mar 15 23:56:48 CET 2006
> I wonder if the goal of pywin32 is to have a comprenhensive interface to
> win32 API, or if the API are implemented on as needed basis.
Both :) I do try and keep it comprehensive (eg, by implementing a complete
family of functions when possible), but the reality is that many API
functions are not covered, and these are indeed added by someone as they
need them. There are a couple of regular contributors that help me out
(most notably Roger Upole - thanks Roger!)
> What would be the process to add API support in that case?
It depends :) In this case I just added that function, as it was simple and
a fairly glaring omission. That doesn't help you though until build 208
comes out, or unless you grab pywin32 from sources and build a copy
... and if you do that, then the process would simply be to add the support
yourself, them mail me (or upload to sourceforge) the patch. Once I get
sick of checking in stuff from you that is generally good, I just give you
CVS checkin permissions and everyone is happy :)
> P.S. What is the official name of this project? pywin32? Python for
> Windows Extensions? I'm a little confused.
And yet more ambiguity - both! :) pywin32 is the short name, where as the
"Python for Windows extensions" is far more descriptive to people not
intimately familiar with our little universe. Certainly pywin32 is much
easier to type ;)
More information about the Python-win32