pywin32: Complete modules using stubgen & stubtest #8866
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the followup to #8825. It does 3 main things:
import win32con
andimport win32com
rather thanimport win32.lib.win32con
andimport win32comext
.). Though both are valid imports.Some modules could not be fully generated with stubgen because of python/mypy#13822 . Some couldn't because
win32ui
needs to be imported first.We can't run stubtest on the CI anyway because of #8660, but if we could, the same mypy issue would result in an error (I had to comment out the imports and delete the modules while testing locally)
* Is there a cleaner way to do this in stubs environment than adding a bunch of top-level modules? Which will result in a ton of
*-stubs
package when installed from PyPI?