Lukasz Balcerzak

@fatal10110 it's hard to say at which point it fails without full stack trace, can you provide one? Also, which Django/Python versions you are using? As to the second issue,...

Hej @schacki, that's actually pretty nice idea. Tests would most probably fail for not-default checker class but we can mark those or make sure they are run with default checker...

Unfortunately with `attach_perms=True` we are first fetching all users with permissions for given object, then for each user a query is performed. This is something marked as `TODO` in the...

So, to sum up, what you'd expect is to have always single query regardless of number of perms codenames passes, right? Will look into that, thanks for this.

@yonkshi thanks, it looks fine. Can you extend documentation? Do you think about something else here (asking as there is still `WIP` in the title)?

@yonkshi docs at manual would be awesome - this and a test seem to be the only pieces before we can merge this.

AFAIR this param was added at some point, thus in order not to introduce breaking change we've left it as "optional" (as pointed by @ad-m already). We can change that...

@fmeurou can you elaborate on your use case? What do you mean by "creating modules"? Do you maybe have some working code or will to prepare a pull request for...

Yeah, it does make sense. However, until now we've been using avro schemas against micro services and our aggregates were easily distinguished by name within single project. I understand that...

well, yeah, it's a pity but I barely find time for django-guardian and cannot work on projector at the moment :/ Plus, I would do this project much differently now...