Fix importing newly-created modules on Python 3 #172
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
Python 3's import mechanism caches the contents of a directory containing modules (such as comtypes.gen) and relies on the "modified time" (mtime) attribute to determine if it needs to reload that directory. In Windows, the mtime is sometimes not updated very often when creating modules in quick succession, which means that the mtime stays identical, which then appears in comtype's case as random module import failures when using a new COM object for the first time.
fxthomas
force-pushed
the
161-fix-modulenotfounderror-stdole
branch
from
4ea51e1 to
07cc8cb
Compare
|
Thank you!! This fixed my recent issue when I upgraded to Office 365! |
This was referenced Sep 17, 2019
|
This is still very much a problem with this library and is causing random failures on Windows. |
5 tasks
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.
Python 3's import mechanism caches the contents of a directory
containing modules (such as comtypes.gen) and relies on the "modified
time" (mtime) attribute to determine if it needs to reload that
directory.
In Windows, the mtime is sometimes not updated very often when creating
modules in quick succession, which means that the mtime stays identical,
which then appears in comtype's case as random module import failures
when using a new COM object for the first time.
See https://stackoverflow.com/questions/52933869/why-does-importing-fails-after-creating-a-module-under-python-3-on-windows for a more detailed explanation.
(Fixes #161)