thenewguy

A use case that cannot be solved by multiple tag models is when you want to do something like: ``` class MyModel(...): tags = TaggableManager() class MyFilter(...): tag = ForeignKey(tagmodel)...

@rtpg I remember thinking that makes sense when reading it. Does this definitely work for you? I seem to get some variation of `HINT: Add or change a related_name argument...

Laughing at myself - read the error message. ``` class Operation(models.Model): add_segments = TaggableManager(through=TaggedAddOperationSegment, blank=True, related_name='foo') remove_segments = TaggableManager(through=TaggedRemoveOperationSegment, blank=True, related_name='bar') ```

Haven't used this past an initial investigation but it does seem to be the solution: ``` class AbstractTaggableManager(TaggableManager): def contribute_to_class(self, cls, name): self.opts = cls._meta if not cls._meta.abstract: if self.remote_field.related_name:...

As far as testing goes - would it be good enough to simply define an abstract and concrete implementation in the models? System checks seem to throw an error with...

Can you look again - it appears to be an error in the client lock() method. The redis-py lock allows the parameter. I checkd before submitting the issue and linked...

@WisdomPill ^

`DefaultClient.lock` does not accept **kwargs and does not list `blocking` as an argument it accepts in the signature

Any solution? I've just hit this problem

@jcass77 are you using this successfully in a production environment?