Skip to content

python project configuration for koji scripts #733

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

glehmann
Copy link
Member

@glehmann glehmann commented Jul 4, 2025

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.

Signed-off-by: Gaëtan Lehmann <gaetan.lehmann@vates.tech>
@glehmann glehmann requested review from stormi and ydirson July 4, 2025 09:21
@glehmann glehmann marked this pull request as draft July 4, 2025 09:22
Signed-off-by: Gaëtan Lehmann <gaetan.lehmann@vates.tech>
@glehmann glehmann force-pushed the gln/koji-build-script-rvln branch from 13a2b2e to 9a30b4e Compare July 4, 2025 09:29
@stormi
Copy link
Member

stormi commented Jul 17, 2025

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

Copy link
Contributor

@ydirson ydirson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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


TIME_FORMAT = '%Y-%m-%d-%H-%M-%S'
from koji_utils.koji_build import main
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could have a comment (and possibly a note printed) telling it is a now deprecated compatibility script?

Alternatively, just using symlinks would be simpler and likely more clear on which script version gets launched (the one in the same repo or the one previously installed). It would also allow to relocate all the scripts into the new package first, and then add the entrypoints.

Comment on lines +11 to +13
[build-system]
requires = ["uv_build>=0.7.19,<0.8.0"]
build-backend = "uv_build"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious, what does this build backend brings over setup_tools? This kind of design choice is useful to note in the commit message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants