Yes. I had my whole dev chapter switch from poetry to uv. We adopted very early (way before uv build was even available) and it has been a blessing. No regrets.
poetry had a bunch of quirks (e. g. the interactive prompt for credentials that frequently gets hidden, tripping up new devs all. the. time.), uses a non-standard project file format (it came out before the standard, but still) and just is incredibly slow.
uv is really fast, you get to pick the build backend, adoption rate is great, it supports a pip - compatible interface, has support to run Python tools separate from the project dependencies and generally has been a pleasure to use.
Don’t get me wrong, having developed Python in the 90s and having lived through easy_install and everything that came after it, I welcomed poetry and used it for years, both personally and professionally. I don’t miss it one day. In fact, I sigh a little every time I stumble upon a project that still uses it.
Yes. I had my whole dev chapter switch from poetry to uv. We adopted very early (way before uv build was even available) and it has been a blessing. No regrets.
poetry had a bunch of quirks (e. g. the interactive prompt for credentials that frequently gets hidden, tripping up new devs all. the. time.), uses a non-standard project file format (it came out before the standard, but still) and just is incredibly slow.
uv is really fast, you get to pick the build backend, adoption rate is great, it supports a pip - compatible interface, has support to run Python tools separate from the project dependencies and generally has been a pleasure to use.
Don’t get me wrong, having developed Python in the 90s and having lived through easy_install and everything that came after it, I welcomed poetry and used it for years, both personally and professionally. I don’t miss it one day. In fact, I sigh a little every time I stumble upon a project that still uses it.