From 56bb7ccf7c2f166b113c4ba72d45738acb4d396d Mon Sep 17 00:00:00 2001 From: Guangyang Li Date: Wed, 16 Sep 2026 23:10:19 -0400 Subject: [PATCH] Remove setup.py and setup.cfg, which no longer do anything Packaging moved to PEP 621 in pyproject.toml. What was left behind: setup.cfg held only `[metadata] license_files = LICENSE`, which pyproject now supplies through PEP 639 `license` and `license-files`. Built the wheel with and without the file: the License-Expression and License-File metadata are identical either way. setup.py was a bare `setup()` call. pyproject declares the build backend and the package list, so nothing reads it. Nothing in the repository referenced either file. Verified every install path rather than only the build: editable (what CI and build.sh use), wheel, sdist, and `pip install .` from the tree, each drawing an icon chart in a clean venv. Also `python -m build` and `twine check` on both artifacts, with metadata unchanged, and the full suite. Editable installs without a 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. --- setup.cfg | 2 -- setup.py | 6 ------ 2 files changed, 8 deletions(-) delete mode 100644 setup.cfg delete mode 100644 setup.py diff --git a/setup.cfg b/setup.cfg deleted file mode 100644 index 8183238..0000000 --- a/setup.cfg +++ /dev/null @@ -1,2 +0,0 @@ -[metadata] -license_files = LICENSE diff --git a/setup.py b/setup.py deleted file mode 100644 index 4ed1f16..0000000 --- a/setup.py +++ /dev/null @@ -1,6 +0,0 @@ -#!/usr/bin/python -# -*-coding: utf-8 -*- - -from setuptools import setup - -setup()