Migrate from Poetry to hatchling + uv

[matthewfeickert]

In #1323 @MattShirley has reported issues with Poetry. In general, Poetry should be avoided (I can give reasons here, but c.f. IRIS-HEP Slack).

A recommendation from @henryiii and myself is to migrate Poetry projects to whatever Python build-system backend makes sense to you + uv. In this case,

ServiceX/pyproject.toml

Lines 1 to 13 in e300d02

	[tool.poetry]
	name = "servicex"
	version = "0.1.0"
	description = "Developmen virtual environment for ServiceX"
	authors = ["Ben Galewsky <ben@peartreestudio.net>"]
	readme = "README.md"
	[tool.poetry.dependencies]
	python = "~3.10"
	servicex-app = {path = "servicex_app", develop = true}
	did-finder-cernopendata = {path = "did_finder_cernopendata", develop = true}
	did-finder-xrootd = {path = "did_finder_xrootd", develop = true}
	did-finder-rucio = {path = "did_finder_rucio", develop = true}

I would just suggest using hatchling and uv.

If you want to have more control over external non-Python dependencies I would suggest using Pixi then.

Happy to provide more information is helpful.

[henryiii]

You can also upgrade to poetry 2, which will get rid of tool.poetry in favor of standards, then the change to another backend is trivial.