> > Yes, I do. > > This is an independent follow-up to the big refactoring we’re talking > about, isn’t it?
Cool. It depends. The cached loader is what I'm least happy with in my refactoring. This internal cache idea I think is simpler, more performant, and easier to understand. Adding it makes the cached loader changes unnecessary. Because the changes to support it are minimal, I'll at least make a side-branch that replaces the cached loader changes with an internal cache. If it pans out and doesn't balloon into further unrelated changes, it might be easier to include it in this refactoring. Preston -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3f0f9cca-ef69-4528-acef-2c4067035606%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
