python project configuration for koji scripts

[glehmann]

We can now uv sync in the dir, and export PATH=$PWD/.venv/bin:$PATH to use koji-build with its required dependency.

The package should also be publishable, allowing, in the future, to pipx install koji-utils to have koji-build and the other tools available in the shell.

Note that I had to move koji_build.py to a module directory. The root koji_build.py now prints a warning saying it's been moved, but we could also not print any warning.

[stormi]

Does this incur a change for current users of the koji_build.py script?

[ydirson]

The info in the commit message would be useful in a README, and maybe uvx can be suggested for install?

[glehmann]

Does this incur a change for current users of the koji_build.py script?

Currently it only display a warning about the file location that has been changed. But that's not mandatory.

[psafont]

What's the point of this file? This version can't be enforced (my system doesn't provide it)

[ydirson]

uv uses it to pin the python version

[glehmann]

What's the point of this file? This version can't be enforced (my system doesn't provide it.

uv should install that exact version for you. That's not the case?

[psafont]

I install tools using uv tool, I've never seen it installing python version.

[ydirson]

Feels strange, as https://docs.astral.sh/uv/guides/tools/ says uv tool run is the same as uvx, and

Tools are installed into temporary, isolated environments when using uvx.

[psafont]

If the system python matches the version allowed in pyproject.toml, I don't see why it would be strange to use the system interpreter