← All tasks
pythondateutil/dateutil #871Not a task: not reproduced

Move all simple constants from setup.py into setup.cfg

envgap__dateutil__dateutil-871

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.
Not a benchmark task.
  • In a clean container the reported failure did not reproduce, or the known fix did not make the project run.

02 / ENVIRONMENT RECIPE

Base commit
84b696a2c396963a7df126f474b1f36239a8f6fa
Manifest
setup.cfg
Reproduce
Awaiting issue-specific recipe
Run under trace
Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

dateutil/dateutil #871 · read the original issue
Nearly all the options in [our `setup.py`](https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files) can be moved over to `setup.cfg`.



The only things that need to stay are:



1. `use_scm_version` (I believe there is no declarative option for this)

2. The README configuration, which involves modifying the README

3. `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](https://github.com/dateutil/dateutil/blob/master/docs/conf.py) 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.
Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched
[]