[issue31058] FileFinder fails to find modules for import if modules are created at runtime and don't result in a directory mtime update

Paul Goins added the comment: Ack; missed that. Thanks, and sorry for the noise. -- ___ Python tracker ___

[issue31058] FileFinder fails to find modules for import if modules are created at runtime and don't result in a directory mtime update

Nick Coghlan added the comment: This is a known limitation of the import caching mechanism, and is the key reason https://docs.python.org/3/library/importlib.html#importlib.invalidate_caches is offered as a supported public API. Ideally, the code that is dynamically creating packages at

[issue31058] FileFinder fails to find modules for import if modules are created at runtime and don't result in a directory mtime update

Changes by Ned Deily : -- nosy: +brett.cannon, eric.snow, ncoghlan ___ Python tracker ___

[issue31058] FileFinder fails to find modules for import if modules are created at runtime and don't result in a directory mtime update

New submission from Paul Goins: If modules are added to a package namespace at runtime, there is a chance that they will not be properly detected if adding the module does not also result in an update to the parent directory's st_mtime attribute. This manifests in not being able to import the