I've never actually used it in any work related projects. I've only used it in personal messing around type projects...
> Good contrib packages tackle issues that that are not trivial, are bikeshed > prone, and are difficult to get right for the common case. I don't think tagging is a particularly hard or non-trivial. Anyway, this conversation is a bit irrelevant because; Core developers want contrib to be slim, so its going to have a really strong usecase to get in. If you start adding 'tagging' a huge number of other things start to feel like they need to be added too. It because a case of well, you added tagging, so why not this? Also, what benefit do we really get from having it in contrib? Ok, so it means everybody has it but by the sounds of things everybody uses it anyway... The difference between it being in contrib and being external is very minimal to the developer that uses it. Dougal --- Dougal Matthews - @d0ugal http://www.dougalmatthews.com/ 2009/5/23 Kai Kuehne <kai.kue...@gmail.com> > > Hi, > > On Fri, May 22, 2009 at 11:52 PM, Dougal Matthews <douga...@gmail.com> > wrote: > > Pretty must everybody does seem to use django-tagging unless they have > some > > special weird use-case. > > Huh? Can you remove that "everybody", please? I've never used tagging > and I'm confident - many others too. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
