Open egeakman opened 8 months ago
Ping @bozhodimitrov
Which advantages/disadvantages can be expected with this approach?
Basically, pyproject.toml
is the modern and standardized way for most Python packages.
Here are some more specific advantages and disadvantages of pyproject.toml
:
Advantages:
hatchling
(unlike setup.py which only supports setuptools
).black
, isort
, ruff
, ... can be directly integrated.Disadvantages:
build
, but it is already the recommended tool (by PyPA) for creating source distributions and wheels.I'm more drawn to using hatchling
these days. Here is an exhaustive answer to "Why Hatch?".
I can edit the PR to use hatchling
instead of setuptools
, just let me know.
Kindly pinging again @stefan6419846. If this project needs more love, I'd be more than happy to help with basic maintenance/triage.
I have no strong opinion on the build tools itself - if you have a look at my own repositories, you will see that I still mostly use the traditional setuptools approach with setup.py
, although with the latest commands. For this reason, I personally do not see the direct need to migrate anything here unless there are actual maintenance benefits.
Leaving this aside: I am just a contributor here, no maintainer/collaborator, thus I am not able to decide this anyway ;) I am sure that the maintainers come back to you once they find appropriate time.
Updates:
Ideas:
hatchling
as the build backendHere is an example project using
hatchling
andpyproject.toml
.To build:
This builds a wheel and a tar under
dist/
, ready to ship.