New to Python packaging? Avoid hatch (danpassaro.dev)

submitted 2 days ago by dan_p_the_dev@lemmy.world to c/python@programming.dev

26 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] eager_eagle@lemmy.world 7 points 2 days ago* (last edited 2 days ago)

you just need only-include

https://hatch.pypa.io/1.13/config/build/#explicit-selection

it's easier than changing build backends

and a lot of times tests/ (and docs/) are included with source code in an sdist format - https://discuss.python.org/t/should-sdists-include-docs-and-tests/14578

[-] dan_p_the_dev@lemmy.world 2 points 2 days ago* (last edited 2 days ago)

Interesting discussion, thanks for the link! I side with pf_moore there; when I think of distributing a library I think of shipping only the library code itself and none of the supporting files, although I can understand the argument to include things like tests/ and docs/.

That said, if you haven't already tailored your project for hatch, configuring only-include is more work than switching to a build backend that just bundles source modules by default. With the right config hatch can do what you like, and I can understand existing users sticking with it, but for newbies I think it's really risky to suggest a build backend that grabs everything it finds in the working directory and packages it up for PyPI. It's just surprising and dangerous default behavior imo.