More ways

uv started out as basically a pip and venv replacement that focused on being fast - fast dependency resolution, fast package installation, fast venv creation. Also it enforced some best practises like refusing to install into system locations - newer pip is also encouraging (but not enforcing, at least not yet) those best practises. There were also a few features that could be helpful for reproducible builds in earlier releases - the big one being the capability to generate a lock file capturing the full set of dependencies at a given point in time and then used to build a new environment (very like poetry's poetry.lock, though not as integrated).

The new features in this release seem to be expanding on that python project level - expanding the support for managing dependencies, adding support for workspaces (collections of packages with their own pyproject.toml, but with a common lockfile - a concept picked up from cargo), and adding a bunch of extra features to support running code from a package in a managed environment. They've explicitly talked about cargo for python as their goal (though not necessarily as a simple "reimplement all cargo features" - there will likely be cargo features that won't make sense in a python context), so I'd say it's likely that they'll expand things to support all the core functionality that cargo has, and then whatever else is needed for python.

I think it's clearly intended to operate in the same space as poetry, though it also operates happily at a lower level - you can still use it as a better pip or python -m venv (which you definitely /can't/ use poetry for). The fact that those lower-level use cases can benefit from things like lockfiles that are created at the higher level will probably be very useful for deployment or image builds and similar (so you don't need poetry and all its dependencies just to deploy a new environment). It's also more standards compliant than poetry - the dependency format follows pep 508, which means you can feed them directly into pip if necessary, which you can't with poetry's dependency format . . .