django-guardian VS Poe the Poet

You can mitigate the pain by using libraries like accesscontrol, express-rbac, django-guardian, etc., to manage authorization more declaratively. But making sure nothing leaks is still a significant challenge.

These pieces fit together very well and are sufficient for replacing most of the goodies Django provides. However, there's one piece missing. Django has a built-in permissions feature, but it's limited to model-level control, i.e., if a user or group has X access to model type Y. Many users have been using the popular django-guardian package to implement row-level permissions. It allows you to establish permissions between users/groups and objects, manages the underlying permission database tables, and provides APIs for configuring and checking such permissions.

https://github.com/django-guardian/django-guardian/issues?q=is%3Aopen+is%3Aissue+label%3ABug

Could use django-guardian for this instead: https://github.com/django-guardian/django-guardian

I was about to use django-guardian until I came across the following in the official documentation:

django-guardian for per object permissions

Compatible with the new pyproject.toml standard, and working well with poetry, there's poethepoet. It's a good alternative, it keeps in the python environment, it's installable through pip(x), and it's cross platform for the windows pythonistas (and there are some, not everyone has more than 1 computer at home...)

I use Poe The Poet https://github.com/nat-n/poethepoet.

So the Poetry maintainer has explained here about why they don’t have the better scripts support you mentioned. However, someone has already built this plugin for Poetry to achieve it.

Poe the Poet, probably.

I've been working on this tool for a while now, which I'm starting to feel is ready for a bit more exposure, it's called Poe the Poet.

nat-n: developer of poethepoet

poe: Not Django-specific, but nice task-runner that uses pyproject.toml