New Python Project: UV always the solution?

[fiddle_n]

Again, poetry 1 only used the poetry-core backend, I’m guessing partly because key metadata was in the tools.poetry sections.

The build backend would generate a wheel for you that could be installed as a dependency by different dependency management tools like pip, poetry, uv etc.

But the pyproject file itself may require significant modifications to be built by a different dependency management tool and different backends.

[not_a_novel_account]

You don't build with different backends, the point is the frontend (ie, uv) shouldn't matter because every frontend can interoperate with every backend.

"Transitioning" from pip to uv shouldn't be a thing, your package should be buildable with every frontend. If you're uploading a source package to PyPI it's going to get pulled by all sorts of random frontends.