Skip to content
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

Refactoring of build management #70

Merged
merged 36 commits into from
Feb 3, 2025
Merged

Refactoring of build management #70

merged 36 commits into from
Feb 3, 2025

Conversation

hkoller
Copy link
Collaborator

@hkoller hkoller commented Jan 30, 2025

Various updates to the build system:

  • Switched the dependency management to uv (fixes Refactor to using uv #31 )
  • Updated CI workflows (related to Python version in CI #24 )
    • Note: some workflow steps are currently disabled (uploads!). We need to re-enable them after the merge.
  • Added tox (related to Python version in CI #24 )
    • ... but not yet activated it in the CI system
  • Added a simple bash script to tag releases

Copy link
Member

@sstroemer sstroemer left a comment

Choose a reason for hiding this comment

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

Minor things I noticed, looks nice!

Two points:

  • We can postpone the Julia version discussion (and refactoring Config to a "better" approach) to a future issue.
  • I think we (= I) should come up with a reduced test set that calls the least amount of small models possible (since those should be tested by IESopt.jl) and just tests the relevant Python functionality, since running tests on all versions might otherwise take quite some time?

steps:
- name: "set UV version"
shell: bash
run: echo "VERSION_UV=0.5.25" >> $GITHUB_ENV
Copy link
Member

Choose a reason for hiding this comment

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

Might that conflict with a fixed uv version that we enforce somewhere else for reproducibility?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This is just here so that all CI steps use the same version of uv (and we can easily change this version in one location).

But I agree, its not optimal. Developers can use different uv versions locally, and I don't think we have any way to control that. It's probably not an big deal anyway, I just wanted the CI build to run with a well-defined uv version.

.github/actions/set-versions/action.yml Show resolved Hide resolved
pyproject.toml Outdated Show resolved Hide resolved
pyproject.toml Show resolved Hide resolved
pyproject.toml Outdated Show resolved Hide resolved
pyproject.toml Outdated Show resolved Hide resolved
Copy link
Collaborator Author

@hkoller hkoller left a comment

Choose a reason for hiding this comment

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

New commits + comments to address the feedback.

pyproject.toml Show resolved Hide resolved
pyproject.toml Outdated Show resolved Hide resolved
pyproject.toml Outdated Show resolved Hide resolved
pyproject.toml Outdated Show resolved Hide resolved
@sstroemer
Copy link
Member

LGTM!

Seems like we can merge this - or is there anything left open that would fit here?

@sstroemer sstroemer merged commit ba91f19 into ait-energy:main Feb 3, 2025
3 checks passed
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.

Refactor to using uv
2 participants