Nearly all the options in our setup.py can be moved over to setup.cfg.
The only things that need to stay are:
use_scm_version (I believe there is no declarative option for this)- The README configuration, which involves modifying the README
cmdclass, which I think has no declarative alternative
The trickiest part will be converting the find_packages option over, but that is covered in the setuptools documentation I linked to, you specify it as packages = find:, and then pass the options in [options.packages.find].
For bonus points, we may be able to switch over the README thing by switching README over to using .. code-block :: python3 directly, and then doing a search-and-replace as part of the docs build instead. This will be a bit tricky, though, because README.rst is included in the docs with an RST include, which means we would have to create a temporary file that would be included. For now, this ticket can be closed if we do everything except that.
Nearly all the options in our
setup.pycan be moved over tosetup.cfg.The only things that need to stay are:
use_scm_version(I believe there is no declarative option for this)cmdclass, which I think has no declarative alternativeThe trickiest part will be converting the
find_packagesoption over, but that is covered in the setuptools documentation I linked to, you specify it aspackages = find:, and then pass the options in[options.packages.find].For bonus points, we may be able to switch over the
READMEthing by switchingREADMEover to using.. code-block :: python3directly, and then doing a search-and-replace as part of the docs build instead. This will be a bit tricky, though, becauseREADME.rstis included in the docs with an RST include, which means we would have to create a temporary file that would be included. For now, this ticket can be closed if we do everything except that.