given that we want to upgrade our setuptools concept and maybe have a conditional requirement as stated in #5400 we should see if we can upgrade to setup.cfg format as docuemnted at https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files.
This new format will allow the code in setup.py that parses __version__ and the README.rst file to be set up declaratively.
We still would be looking to maintain our C-extension fallback building approach and w would still have the extra run_setup() indirection going on in setup.py.
I haven't tried it yet but I am assuming we can send programmatic options to setuptools.setup(), which currently include cmdclass, distclass. find_packages it looks like they have a declarative version of that for setup.cfg.
I also want to attempt to understand what's going on with our custom Distribution class and see if we still need to be doing this in that way.
given that we want to upgrade our setuptools concept and maybe have a conditional requirement as stated in #5400 we should see if we can upgrade to setup.cfg format as docuemnted at https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files.
This new format will allow the code in setup.py that parses
__version__and the README.rst file to be set up declaratively.We still would be looking to maintain our C-extension fallback building approach and w would still have the extra run_setup() indirection going on in setup.py.
I haven't tried it yet but I am assuming we can send programmatic options to setuptools.setup(), which currently include cmdclass, distclass. find_packages it looks like they have a declarative version of that for setup.cfg.
I also want to attempt to understand what's going on with our custom Distribution class and see if we still need to be doing this in that way.