I have three concerns with caching at present. 1. Caching generates a lot of files in the .leo/db folder. My present .leo/db folder contains about 27 meg of data. I am concerned about the size of the folder. It looks like it has no natural size limit.
2. At present, Leo does not cache expansion bits. It definitely should. Today I realized that the rc1 deadline was improperly preventing me from fixing this. 3. I have concerns about path.py and pickleshare.py for Python 3.x. I got them working with a few hacks, but these files must definitely work properly and I can't guarantee that. It's troubling that there are no unit tests. It may be possible to limit the size of the .leo/db folder while eliminating the dependence on path.py and pickleshare.py. That's not a requirement, however. I don't have time to elaborate further now. More to come later today. Ville, I won't do anything about caching without your comments and approval. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
