sebastien requiem

The way I solve that for now is by doing : ``` class Game(models.Model): _players_id = None @property def players(self): if _players_id is None: self._players_id = Set("%s:%s:players_id" % (self.__class__.__name__, self.id)...

That is definitely worth looking at. Do you fancy creating a pull request for testing that out maybe ? We also have to consider the amount of time lost in...

So I got to look at Ohm behavior. It seems that they haven't decided to take the "duplication" approach. We may want to do the same in Redisco. I will...

I think that we are getting there in term of interoperability except for the filtering keys, which are temporary anyway. It's a good reminder that you send since I am...

This should happen now since we have unit tests back on track.

Beware that it will have a new name as the the creator of the project lost his pypi account a looooong time ago. In the mean time, I encourage you...

Although, remember that `0.2` is not compatible with `v0.1.4` that you may be using at the moment. I should maybe write a small migration tool for this.

I am afraid not. Since this is _the same_ project all in all (we really share a lot of common code). But since pypi wont allow us to publish any...

I find that globally useful but I'd rather have to configure the `modelset` to have all operations fetched in a (or in fact two) pipeline(s). But Redisco should offer such...

Not yet. @jkbr and I discussed the need for such a function but I would like something a bit more transparent than another function call on the modelset.