Skip to content

Conversation

@joker-at-work
Copy link
Contributor

Instead of setting description, name etc. in setup.py and setup.cfg, we switch to only setting them in setup.cfg. While using setup.py for this is still supported, the standard a couple years back was using setup.cfg - and now we moved off to pyproject.toml.

The reason for this change is, that automatic Python package building with hatch fails in our CI. Removing these settings makes it work.

Instead of setting description, name etc. in `setup.py` and `setup.cfg`,
we switch to only setting them in `setup.cfg`. While using `setup.py`
for this is still supported, the standard a couple years back was using
`setup.cfg` - and now we moved off to `pyproject.toml`.

The reason for this change is, that automatic Python package building
with `hatch` fails in our CI. Removing these settings makes it work.
@joker-at-work joker-at-work requested a review from notque as a code owner December 5, 2025 14:32
Copy link
Contributor

@notque notque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added the metadata for discovery on PyPI. Otherwise, straight forward and reasonable. I approve. I am on vacation, so I will hand it to you to communicate, and get the additional approval.

@fwiesel fwiesel self-requested a review December 6, 2025 19:51
@joker-at-work joker-at-work merged commit 1a3edfb into master Dec 8, 2025
1 check passed
@joker-at-work joker-at-work deleted the remove-setup-py-settings branch December 8, 2025 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants