New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pyproject.toml Migration #1901

Open

ulgens opened this issue Jan 24, 2025 · 1 comment

Contributor

ulgens commented Jan 24, 2025

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.

Contributor Author

ulgens commented Jan 24, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment