Skip to content
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

Adopt declarative config (setup.cfg or pyproject.toml) #555

Closed
jaraco opened this issue Jun 7, 2024 · 1 comment · Fixed by #557
Closed

Adopt declarative config (setup.cfg or pyproject.toml) #555

jaraco opened this issue Jun 7, 2024 · 1 comment · Fixed by #557
Assignees
Milestone

Comments

@jaraco
Copy link
Collaborator

jaraco commented Jun 7, 2024

I am also aware that it is not recommended to have a large amount of code written in setup.py as it is now. I confess that I do not know much how to properly replace (or abolish) things like class test(Command) and class post_install(install) when adopting more modern ways such as pyproject.toml or setup.cfg.

Originally posted by @junkmd in #216 (comment)

@jaraco
Copy link
Collaborator Author

jaraco commented Jun 7, 2024

We can incrementally move metadata from setup.py to setup.cfg and decide if the remaining features in setup.py are needed. We can also use this as an opportunity to modernize other packaging concerns (like declaring the non-legacy setuptools backend).

@jaraco jaraco self-assigned this Jun 7, 2024
@junkmd junkmd added this to the 1.4.4 milestone Jun 7, 2024
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 a pull request may close this issue.

2 participants