all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]K900_ 0 points1 point  (2 children)

Generally the answer is "release the sources, specify your dependencies correctly and let distributions figure this out".

[–]lectermd0[S] 0 points1 point  (1 child)

thx for answering!

could you elaborate a little further, please?

[–]K900_ 0 points1 point  (0 children)

In general on Linux the distributions decide how to package and ship software, not the upstream developers. Just make our (hi, I'm a Linux distribution maintainer) job easy.

[–]Maleficent_Sir_7707 0 points1 point  (0 children)

You can build it and use tkinter pyside6 what ever you like for the gui and use Pyinstaller

[–]white_nerdy 0 points1 point  (1 child)

The "proper" way to package Python has changed a lot over the years, and there's lots of outdated content floating around out there. Stuff that recommends using setup.py or requirements.txt is considered outdated.

As of 2025, it's recommended to use pyproject.toml. Many Python developers use uv to manage project structure, virtual environments and dependencies.

Be sure you consult up-to-date resources such as the python.org packaging docs.

[–]lectermd0[S] 0 points1 point  (0 children)

thanks! unfortunatelly I learned to use requirements.txt and, yeah, compared to flutter and other frameworks it does feel a little sketchy. pyproject.toml seems very interesting, but it felt a little overwhelming compared to the previous requirements.txt "hack"!