Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If I'm not building a shared library, what is the benefit of having my project as a package? It seems Rye only supports python packages, but most my stuff never touches PyPI or anything similar.


For that use-case, you can set up a `virtual project` using Rye. And use it just to create python envs, and sync dependencies.

Honestly, the biggest time-saver for me has been Rye automatically fetching python binaries that work everywhere, and setting up clean venvs.

- https://rye.astral.sh/guide/virtual/


Rye is a python only thing, and if you're using python without any external dependencies, it probably doesn't have that much benefit (although it does make having different python versions for different projects a lot cleaner if you need that).

I think that it has a huuuuge benefit for applications as well as libraries. Rye generates lock files, which are really handy for pinning down versions of something running in production so that it'll behave predictably.


I am using external dependencies I’m just usually not packaging my project.


Some OSes need shims to easily call scripts on the command line. Also, you can define multiple entry points that might live in one big ol file.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: