-
Notifications
You must be signed in to change notification settings - Fork 556
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
migrate setup.py to pyproject.toml #1465
migrate setup.py to pyproject.toml #1465
Conversation
Thanks for the PR @deronnax , this has been overdue for some time. CI is not happy with the change though, do you think you could figure this out, or need help? Our CI workflow is pretty simple, so I'm surprised there's been a hiccup: https://github.com/dbcli/pgcli/blob/main/.github/workflows/ci.yml but perhaps we're missing something there. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have left a few comments from a (very) cursory review. I'll make a second pass in the coming days to make sure that the new pyproject-based version is equivalent to what was set in setup.py
.
41c8be9
to
e647319
Compare
a0d71f3
to
9284371
Compare
9284371
to
94c0911
Compare
All concerns addressed. Sorry for the oversights. |
@j-bennet let's merge ? |
@deronnax Yes! thanks for the ping. |
Description
Following PEP 621, setup.py is soft-deprecated (not truly deprecated but not the way to go anymore) and metadata in pyproject.toml is the new norm. This change should be functionally strictly equivalent.
Checklist
changelog.rst
.AUTHORS
file (or it's already there).pip install pre-commit && pre-commit install
), and ranblack
on my code.