Remove setup.py and setup.cfg, which no longer do anything

[gyli]

Packaging moved to PEP 621 in pyproject.toml. These two files stayed behind and no longer do anything. Nothing in the repository references either of them.

setup.cfg held only:

[metadata]
license_files = LICENSE

pyproject.toml now supplies that through PEP 639 license = "MIT" and license-files. I built the wheel with and without the file and compared the metadata:

with setup.cfg     -> License-Expression: MIT, License-File: LICENSE
without setup.cfg  -> License-Expression: MIT, License-File: LICENSE

setup.py was a bare setup() call. pyproject.toml declares build-backend = "setuptools.build_meta" and [tool.setuptools] packages, so nothing reads it.

Verified every install path, not just the build

The risk with deleting setup.py is editable installs, which CI uses in five jobs and build.sh uses too. So I exercised each path in a clean venv, installing with the [icons] extra and drawing an icon chart:

path	result
pip install -e ".[icons]"	drew 50 icons
wheel	drew 50 icons
sdist	drew 50 icons
pip install ".[icons]" from the tree	drew 50 icons

Plus python -m build and twine check on both artifacts with identical metadata, and the full suite (234 tests).

Two notes

Editable installs without setup.py use PEP 660, which needs pip 21.3 or newer. Every CI job gets pip from actions/setup-python, which is far past that, and build.sh runs pip install --upgrade pip first.

The sdist still contains a setup.cfg, but it is not this one. setuptools generates its own during the sdist build:

[egg_info]
tag_build =
tag_date = 0

I checked this after noticing the file still appeared in the archive listing. Worth recording so nobody deletes ours a second time thinking it did not take.