On Sep 11, 2008, at 6:44 AM, C. Titus Brown wrote:
> > Hi, Namshin, > > Chris checked in a few patches of mine last night, and several of them > had to do with caching. One that almost certainly is affecting you is > my removal of 'clear' from AnnotationDB -- it now returns an error, as > it should, because AnnotationDB is a read-only database! I think we > should add a new function, 'clear_cache', which does what 'clear' used > to do: remove the cached AnnotationDB objects. How does that sound? Your proposal matches what I proposed in May (tracker issue #6, http://code.google.com/p/pygr/issues/detail?id=6&can=7) that we add a clear_cache() method as a standard across all database interface classes. Let's implement it. Regarding, Namshin's error report, I only pushed your changes to the public git repository around 8:30 pm last night, so it's not clear that his report is due to those changes. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
