Skip to content

pyproject.toml Migration #1901

@ulgens

Description

@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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions