Patch: add a TagField object for more natural use of tags. about django-tagging HOT 9 CLOSED

Fantastic stuff - thanks, Jacob.

Added in revision 28.

Keeping this open until I add the docs for it.

Currently, this will blow up when you try to assign tags when initially 
creating an
object, as it hasn't been saved yet when __set__ is called.

Is this something that can be worked around?

Ah, that's because the object doesn't have a primary key yet. Let me explore 
how I
might defer setting tags until later...

OK, attached is a first stab at making tag assignment to unsaved items work. 
It's a
pretty nasty hack, though, so we should spend a bit of time looking for better 
options.

That last nasty patch had a bug in it; attached is a fix.

It's still nasty, though.

Applied the patch in revision 33 - I applied the goggles while checking the 
patch in,
but they did nothing :)

This seems to throw an AttributeError when trying to delete a tagging instance. 
It seems to be calling an 
attribute '__tags_save_defered_tags' which no longer (or never did) exist.

After looking at `delete_objects` in django.db.models.query, I've modified 
`TagField`
in revision 36 to delete tags when the `pre_delete` signal is dispatched.

The `delete_objects` function sets the primary key attribute to `None` before
dispatching the `post_delete` signal, but we need the primary key to be on the
instance when making the call to `TagManager.update_tags`.

Patched again in issue 13.