[Python-Dev] Planning on removing cache invalidation for file finders (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Sat Mar 2 16:37:56 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 Sun, Mar 3, 2013 at 1:36 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
It's that case where the process that added the modules is separate from the process scanning for them, and the communication is one way, where the heuristic is important. Explicit invalidation only works when they're the same process, or when they're closely coupled so the adding process can tell the scanning process to invalidate the caches (our test suite is mostly the former although there are a couple of cases of the latter).
s/are/may be/ (I don't actually remember if there are or not off the top of my head)
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- 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 ]