-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modernize setuptools support to use pyproject.toml #184
Conversation
Replace the obsolete `setup.py` script and `setup.cfg` configuration file with the modern PEP 621 `pyproject.toml` metadata. This also implies replacing the custom version/long-description grabbing logic (that is broken with Python 3.12) with the features nowadays built-in in setuptools. Fixes Knio#172
Thanks! but can you try to get the remaining CI passing? I give up for now. |
I can fix 3.12 but FWICS testing against 2.7 is no longer possible with GHA. |
58a6c82
to
d4a400a
Compare
Ok, I think that's as far as we can reasonably get. Python < 3.7 is no longer supported by setuptools even. |
Thanks, this seems to work in CI, but I can't actually build a package locally to publish, as it just makes "UNKNOWN" $ python3 -m build --no-isolation
* Getting build dependencies for sdist...
running egg_info
writing UNKNOWN.egg-info/PKG-INFO
writing dependency_links to UNKNOWN.egg-info/dependency_links.txt
writing top-level names to UNKNOWN.egg-info/top_level.txt
reading manifest file 'UNKNOWN.egg-info/SOURCES.txt
...etc any ideas? $ python3 --version
Python 3.9.2
$ python3 -m build --version
build 1.0.3 (/usr/local/lib/python3.9/dist-packages/build) |
Thanks! |
Thanks for the PR, any chance cutting off a new release? Thanks! |
Replace the obsolete
setup.py
script andsetup.cfg
configuration file with the modern PEP 621pyproject.toml
metadata. This also implies replacing the custom version/long-description grabbing logic (that is broken with Python 3.12) with the features nowadays built-in in setuptools.Fixes #172