Proposal to switch from poetry to uv ?

[ticosax]

In the context of #47

Motivation

Assuming Keeping django-fsm-log as opt-in is something we want to preserve.
It looks like concept of workspaces could be the right abstraction to deal with plugins that would extend default functionalities of django-fsm-2.
If we go through the idea of moving django-fsm-log in this project, we could offer it as opt-in to users, while still preserving comfort of maintenance within a central repository.

Folder structure would become

# main project
pyproject.toml
django_fsm/...

# opt-in only, packaged separately, are all dependent of `path = ../django_fsm`
packages/django_fsm_logs/pyproject.toml
packages/.../pyproject.toml

workspaces being only supported by uv, it would require to replace poetry with it.

[pfouque]

Maybe we don't even need uv to create an opt-in plugin (especially if we're only providing abstract models)

But I was already thinking about giving uv a try, it was just not a priority at the moment.

If someone publishes a PR with workflows updated (and a "how to contribute" in the README) It will be accepted! 😉

[pfouque]

Maybe we do need in fact.
I was assuming that adding django_fsm to INSTALLED_APPS but it's required as soon you want to integrate the admin or the graph_transition command.
And I wouldn't like to create tables in the database just for that, unless explicitly enabled.