#30948 closed Cleanup/optimization (fixed)
Change packaging to use setup.cfg declarative syntax
| Reported by: | Jon Dufresne | Owned by: | nobody |
|---|---|---|---|
| Component: | Packaging | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
setuptools feature: https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files
Available since setuptools 30.3.0 (8 Dec 2016).
Using setup.cfg reduces boilerplate and logic in setup.py. As setup.cfg is a simple data format, it could allow for automation with external tools in the future.
Change History (9)
comment:1 by , 5 years ago
| Has patch: | set |
|---|
comment:2 by , 5 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
I think this will make things much easier. Even setuptools itself does this now.
By the time Django 3.1 is released, this will have been supported for nearly 4 years.
comment:3 by , 5 years ago
| Patch needs improvement: | set |
|---|
PR has grown in scope to incorporate a few things. (License change, other clean ups, ...) If we can pull that out separately, we can assess this change on it's own. (Thanks for the effort — looks good.)
comment:4 by , 5 years ago
| Patch needs improvement: | unset |
|---|
Feedback addressed and reduced PR in scope.
comment:5 by , 5 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
https://github.com/django/django/pull/12013