add _post_coinit subpackage
#571
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- move `unknwn` into `_post_coinit` - add `_post_coinit` to `setup.cfg`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have been working on reducing the weight of
__init__.pysince #559, but the number of files placed directly undercomtypes/has also increased.During the initialization of the package, not all modules under
comtypes/are loaded, only a limited number of modules, such asGUID.py.It can be difficult to see at a glance which modules are needed during initialization, which can create a new cognitive load.
With this change, to make it easier to understand what modules are needed during initialization by consolidating symbols that should be defined after the call to
CoInitializeEx, or symbols where the order of definition does not matter during initialization, into the_post_coinitsubpackage.