Make is possible to swapout Tag models about django-taggit HOT 5 CLOSED

+1 on this. We need tags to be memcacheable, and this is one piece of the puzzle.

from django-taggit.

I'm curious what you mean about making tags "memcachebale"?

from django-taggit.

For performance, we store the results of most of our queries in memcached using django-cache-machine. django-cache-machine inserts itself into the query process by means of a custom manager, which we must make the default manager of every model class. Short of monkeypatching (which I hate because it's hard to notice by looking at the code), we would need to not only subclass most of taggit's managers and models (fine) but also override any method in any of them that refers to any of the others. For example, TaggedItem.tags_for() refers to Tag by name, and we'd have to change it to point to our CachedTag class that has the caching custom manager.

Of course, this all points to a more general problem in Django—it doesn't have a component architecture (e.g. peak.binding or Zope-style components) and so makes this sort of loose coupling a one-off problem for everybody. I'm honestly not sure what the best solution is, so if you have any thoughts, I'm all ears!

from django-taggit.

I've got a branch with support for this and I've solicited feedback on the mailing list: http://groups.google.com/group/django-taggit

from django-taggit.

With the merger of the api-refactor branch this is possible.

from django-taggit.