Hi Russell, I was away and arrived back too late for this to matter, but for the sake of the archives, I just had a couple of comments:
> Module-based configuration: > --------------------------- > > * The aesthetic of user-configuration options is cleaner because > configuration items are shorter and don't require duplication of > terms. e.g., django.core.cache.backends.locmem.LocMemCacheBackend > duplicates the 'locmem' bit for no real end-user gain unless you're > planning to have a non-locmem backend in the locmem package. One of the systems i.e. the authentication backend actually doesn't have this problem, due to putting all the provided backends in a single backends.py. We could do the same for other systems by adding imports. However, that would be a bad idea IMO - by having the classes separated, and without imports, you can reduce memory usage for the common case of having certain backends that are never used and therefore never loaded into memory. But the memory usage issue is another general argument in favour of your 'one module per backend' ideal, especially for large backends that you are unlikely to need more than one of. > I hope I've done a reasonable job of summarizing the two positions > in an unbiased way. Yes, thanks :-) I had another argument in favour of class based, which is that it makes the source code slightly more greppable from the point of view of someone new to Django and a Django project: as a non-Django Python developer, if I worked on a project that had a MessageStore class, I would normally find out where it is used by grepping for 'MessageStore'. With the module based system, that could come up with nothing, which is puzzling, but with the class based you will at least find a line in settings.py, which gives you something to google. Cheers, Luke -- "If something is hard, it's not worth doing." (Homer Simpson) Luke Plant || http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en.
