> Indeed, this is correct. It appears to be a bug in the cache code, its > updating the cache retrieval code for new keys when you add settings > (this is why key3 uses the createfunc), but its not updating it for > existing keys you've retrieved (which is why key1 fails still later).
Yes. I think it's not right to update values (such as 'kwargs', 'createfunc') through this kind of cache hierarchy. > > The proper behavior is that the createfunc should only be used for > keys you've asked get_cache for with createfunc in the past. So key3 > should fail in addition to key1, since the createfunc was only > specified for key2. Is that the behavior you were expecting as well? Yes. That is behavior I'm expecting. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
