A while ago I was picking through the cache system and found a few things that seemed like they could use cleanup. I'm interested in hearing thoughts on which of these might be worth pursuing, whether today or later.
* The "simple" backend seems obsolete. The newer "locmem" is functionally equivalent for the user, but is suitable for deployment as well as development. Should "simple" be removed? This might allow refactoring of the backend code to simplify its inheritance structure. * "cull_percentage" is called "cull_frequency" inside the code; neither is a great name, but the second is better. Worth changing? * A documentation question: Does "manage.py createcachetable" create an indexed table? if so, we don't need to repeat their admonition about making sure the table's indexed. * Should the "file" backend's _file_for_key method be rewritten to use hashes instead of cleaned-up strings? It fails to correctly handle an empty string, which is a valid string and dictionary key otherwise. In any case, looking forward to a few hours of Django hacking today... pb -- Paul Bissex <[EMAIL PROTECTED]> Northampton, MA 01060 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
