Skip to content

Remove committed uv.lock so the env resolves the latest ogcore #116

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.

Sign up for GitHub

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

Closed
SeaCelo wants to merge 1 commit into from
+2 −3,104
Closed

Remove committed uv.lock so the env resolves the latest ogcore #116

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,3 +45,4 @@ docs/book/_build/*
*ogzaf_example_output.csv
*/OG-ZAF-Example/*
*un_api_token.txt*
uv.lock
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,6 @@ OG-ZAF is a South Africa country calibration of the OG-Core overlapping-generati

## Repo conventions

- `pyproject.toml` is the source of truth for dependencies. `uv.lock` pins exact versions across machines and is checked in.
- `pyproject.toml` is the source of truth for dependencies, declared as floors (e.g. `ogcore>=…`). `uv.lock` is not committed (it is git-ignored), so `uv sync` resolves the latest compatible versions — including the latest released `ogcore`.
- The packaged JSON default parameters are the standard baseline input for offline/default runs.
- Calibration or data-source changes (macro parameters, demographics, earnings, industry I/O) should be validated with targeted tests and, where feasible, the relevant example flow.
Loading
Loading