I can confirm that the lock.release is back. Thanks! One minor suggestion, your valuable comments which come from many test and efforts, are worthy to be put into CacheInRam.__call__() 's doc string or comment. Do you think so?
On Nov8, 12:34am, mdipierro <[email protected]> wrote: > Turns out the deepcopy has some problems: > 1) breaks backward compatibility > 2) it is limiting because people may want to cache live objects > 3) it cannot work unless we deepcopy no storage and retrival which > would make things slow. > > Please check trunk again. I think the release is back. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
