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

Move from setup.py to pyproject.toml #611

Open
AnesBenmerzoug opened this issue Jul 8, 2024 · 1 comment
Open

Move from setup.py to pyproject.toml #611

AnesBenmerzoug opened this issue Jul 8, 2024 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers light task A light task packaging Library packaging and releasing

Comments

@AnesBenmerzoug
Copy link
Collaborator

Now that pyproject.toml is the standard and it can almost everything that can be done with setup.py, we should consider using it exclusively. The main thing with pyproject.toml is it is declarative as opposed to setup.py which is procedural.

The switch would additionally open the door to using other tools such as hatch to (See here for a list and description of its advantages over setuptools and other tools)

At the very least we could move all the static metadata (e.g. package name, authors, description, license) from setup.py to pyproject.toml.

@AnesBenmerzoug AnesBenmerzoug added enhancement New feature or request good first issue Good for newcomers light task A light task packaging Library packaging and releasing labels Jul 8, 2024
@janosg
Copy link
Collaborator

janosg commented Jul 9, 2024

I like the idea. Also want to put everything into pyproject.toml in my other projects, just haven't got around yet. I have no experience with hatch but friends of mine have already switched and it looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers light task A light task packaging Library packaging and releasing
Projects
None yet
Development

No branches or pull requests

2 participants