Mark Hammond
Mark Hammond
LGTM, ok with you @vernondcole?
I'm not sure what `win32.win32gui` is - `win32gui` is a top-level module - there's no `win32` parent in pywin32.
See https://github.com/mhammond/pywin32/blob/main/README.md#troubleshooting for some ideas
Thanks for your interest! A .d file is like any other autoduck file, but instead of being embedded in c++ source files it's a stand-alone file. Autoduck is somewhat like...
I have no plans here at all - these .exe artifacts have been downloaded many thousand times for the latest release, so I'll keep them alive as long as practical,...
I'm open to that, but I'm not quite sure what you are proposing yet - can you please outline what such a PR would look like?
That sounds reasonable to me, although it is worth noting that the build process generates many HTML files from autoduck comments in the source-code and from various .d file spread...
Docs are included in the package. There are no web-hosted docs (although I'd be happy to accept a PR which works out how to publish them on github)
> > Docs are included in the package > > I looked for it and found https://github.com/mhammond/pywin32/tree/master/AutoDuck Sorry, I meant that the docs are built and included in the installation...
> IMHO it's a good idea to create a docs direcotry in the git repo root and add markdown or ReSt files there... Or setup the full stack with sphinx...