migrate to setup.cfg

[deronnax]

An initiative of my own. Setup.py is a thing of the past and will soon be gone, and declarative config is superior and recommended by setuptools. I am polishing it on my fork and will remove the "draft" label when done.

[johnthagen]

Porting to pyproject.toml is likely the preferred thing to do here if modernizing in the goal

• https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html

[deronnax]

I'll make you that, it's just few minutes of more work. Stay tuned.
update: @johnthagen are you a core maintainer? Do you have the capability to merge this supplemental work you are asking for?

[johnthagen]

@deronnax No, not a core maintainer, just someone who has contributed to drf-spectacular in the past and noticed this MR and have experience with modern packaging tools.

[tfranzel]

Hi y'all,

the reason I have not approached this is because python packaging is fickle. Anybody that has ever messed with include_package_data and MANIFEST.in probably knows this all to well. I know this approach is outdated, but it works. Maybe the new tools work just fine, but I almost got PTSD from packaging before. So we must check the difference of both the the source build as well as the wheel (including structure and all contained files)!

I think if porting, we should go directly to pyproject.toml as John said, instead of updating from the outdated solution to the semi-outdated solution.

[deronnax]

@tfranzel I'll do you the move to pyproject. Assign the issue to me please.

[tfranzel]

@deronnax yes please give it a shot. You can either do a new PR or change this one. Since this is already your PR, there is no need to assign you to it.