[Python-Dev] Planning on removing cache invalidation for file finders
Antoine Pitrou
solipsis at pitrou.net
Sun Mar 3 02:16:30 CET 2013
More information about the Python-Dev mailing list
Sun Mar 3 02:16:30 CET 2013
- Previous message: [Python-Dev] Planning on removing cache invalidation for file finders
- Next message: [Python-Dev] Planning on removing cache invalidation for file finders
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, 2 Mar 2013 11:16:28 -0500 Brett Cannon <brett at python.org> wrote: > > In addition, it may be appropriate for importlib to offer a > > "write_module" method that accepts (module name, target path, > > contents). This would: > > > > 1. Allow in-process caches to be invalidated implicitly and > > selectively when new modules are created > > I don't think that's necessary. If people don't want to blindly clear all > caches for a file they can write the file, search the keys in > sys.path_importer_cache for the longest prefix for the newly created file, > and then call the invalidate_cache() method on that explicit finder. That's too complicated for non-import experts IMHO. Regards Antoine.
- Previous message: [Python-Dev] Planning on removing cache invalidation for file finders
- Next message: [Python-Dev] Planning on removing cache invalidation for file finders
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list