pyproject.toml Migration

[ulgens]

I feel like I'm abusing the issues feature but I hope it's okay, considering we don't have discussions enabled.

Is there a plan to switch to a pyproject.toml file? I think it's important because

• It gives the impression that the project is modern. If not for anything else, I believe that it's important that projects under django organization should look modern and up to date.
• Easier to use and manage. Especially with uv, almost everything is collected under a single tool and single configuration file.

and that's all 🙂 I was hoping to write something better, but I think that development ergonomics are important enough for a change like this one.

[ulgens]

There is a template project that I test these types of practices on it first. I studied the poetry - uv migration on that repo and I'm happy with the results: https://github.com/ulgens/django-blasphemy/pull/603/files If that seems okay, I can adapt a similar pattern on this repo too.

[alexgmin]

Just want to add that this tool should make it easier to migrate to uv from the current setup.
https://github.com/mkniewallner/migrate-to-uv