Migrate morango to uv for package management by bjester · Pull Request #296 · learningequality/morango

bjester · 2026-03-19T22:11:43Z

Summary

Converts projet to project.toml format
- Consolidates requirements into project.toml
- Sets it up to use setuptools-scm which uses repository tags for versioning
- The build should look at the most recent tags for the parent, hopefully to ensure we can release from different release branches
Migrates the project to uv for dependency management and builds
- Updates all testing workflows to pre-build the wheel using python 3.9, which mimics our build process
- EOL python workflows continue to use python image, and all others use uv to set up python
- Uses uv build to generate the distribution files
- Uses --installpkg with pre-built wheel for tox to avoid having it build Morango itself, and the issues that causes with EOL versions of python
Updates the Read the Docs build to use uv
Migrates the project to use prek instead of pre-commit
Adds some README documentation about getting set up for development

TODO

Have tests been written for the new code?
Has documentation been written/updated?
New dependencies (if any) added to requirements file

Reviewer guidance

We'll have to test the release process manually, unless there's a different suggestion.
I verified the built wheel file does not contain any unnecessary files not present previously

AI usage

Local AI was used to do the initial migration. Claude was used to verify the approach, and make some corrections. Finally, manual trial and error were needed to fix what AI could not.

marcellamaki

I have added some questions, which I think reflect more about my non-understanding of morango and python version management than anything about uv in particular 😂 thank you for bearing with be @bjester

marcellamaki · 2026-03-20T16:58:31Z

.github/workflows/check_migrations_sqlite.yml

          github_token: ${{ github.token }}
-          paths: '["morango/migrations/*.py", ".github/workflows/check_migrations_sqlite.yml", "setup.py", "requirements/*.txt"]'
+          paths: '["morango/migrations/*.py", ".github/workflows/check_migrations_sqlite.yml", "pyproject.toml"]'
+  build:


just want to see if i'm understanding this well from the reviewer guidance. so this part is new because it gives us more similarity (and.... therefore increased confidence?) to the build process for morango releases?

Yeah this is the result of the complexity in that with older versions of python, we can't simply use pip install . for Morango having the more modern pyproject.toml. It needs more modern build tools that don't support older versions of python.

Morango's build and publish always uses python 3.9, so this mimics that to create a wheel file which CAN be installed later (line 88):

pip install $(ls dist/*.whl | head -n 1)[test]

$(ls dist/*.whl | head -n 1) this is just a subshell to use globbing since pip wants a full file name

[test] this tells pip to install the test extras defined in the pyproject.toml

So the result is that this is indeed more realistic tests by testing the wheel that we'd publish (built on 3.9) instead of building a wheel within each python version being tested.

Interesting - this might make doing a parallel version in Kolibri slightly more challenging, because there we build the whl file in Python 3.6 to bundle the dependencies (I am sure we'll find a work around, but this is good extra context).

marcellamaki · 2026-03-20T17:00:02Z

.github/workflows/tox.yml

    steps:
      - uses: actions/checkout@v6
-      - name: Set up Python ${{ matrix.python-version }}
+      - name: Download wheel artifact


and here, it uses that whl to help with the python version management that you were describing

Yeah this copies that wheel file artifact to make it available to this step.

marcellamaki · 2026-03-20T17:01:13Z

README.md

+
+To start contributing to Morango, first make sure you [have `uv` installed](https://docs.astral.sh/uv/getting-started/installation/).
+
+Create a virtual environment, with at least python 3.9:


Yeah is this confusing? Perhaps it should just use 3.9. This is the minimum for build tools

I think the "at least 3.9" and then having it use 3.10 is what confused me. if using 3.10 is better, maybe just adding a little bit of extra detail to the comment about why that's preferable (but confirming that 3.9 still works)? that said, i definitely am not someone who has a lot of context here, so this might be much more apparent to you and others (prathamesh, richard) who are working with morango more consistently. it's definitely not a blocker, just a thought

Yeah I think I should update to say 3.10. Python 3.9 is technically EOL already!

marcellamaki · 2026-03-20T17:02:19Z

pyproject.toml

+maintainers = [{name = "Learning Equality", email = "dev@learningequality.org"}]
+readme = "README.md"
+license-files = ["LICENSE"]
+requires-python = ">=3.6,<3.15"


so we are still supporting those versions, we are just using 3.10 as the default now?

The build tools require at least 3.9, which is what we used to build and publish the wheel before these changes. So yes the installation still supports these versions, just that development needs newer versions.

got it - thanks!

rtibbles

Code changes make sense - I did some spot checks on the different CI jobs, and all the tests seemed to be running with the correct packages installed and on the right Python versions, so all the changes seemed to have successfully maintained what is required!

rtibbles · 2026-03-20T17:24:09Z

.github/workflows/check_migrations_sqlite.yml

          github_token: ${{ github.token }}
-          paths: '["morango/migrations/*.py", ".github/workflows/check_migrations_sqlite.yml", "setup.py", "requirements/*.txt"]'
+          paths: '["morango/migrations/*.py", ".github/workflows/check_migrations_sqlite.yml", "pyproject.toml"]'
+  build:


Interesting - this might make doing a parallel version in Kolibri slightly more challenging, because there we build the whl file in Python 3.6 to bundle the dependencies (I am sure we'll find a work around, but this is good extra context).

rtibbles · 2026-03-20T20:00:52Z

.github/workflows/check_migrations_sqlite.yml

  migration_test:
    name: SQLite migration tests
-    needs: pre_job
+    needs: [pre_job, build]


I don't think it's a concern in morango - but once concern I've had in Kolibri is that our workflows are overly granular.

I've experimented with having more top level "CI" in some repos recently - so that our CI checks become more of a cascade (make sure it builds first, then test kind of thing).

With no good way in Github Actions to group workflows better, I am tempted to do more of this - but morango doesn't have enough for this to be a concern!

rtibbles · 2026-03-20T20:02:33Z

pyproject.toml

+[project]
+name = "morango"
+dynamic = ["version"]
+description = "Pure Python sqlite-based Django DB replication engine."


Is it SQLite based? :)

(I know this is copied, but just funny given how much work we've done to make sure it works on postgres too!)

Haha good catch

bjester force-pushed the uv-migration branch 5 times, most recently from 8983157 to 90953b5 Compare March 19, 2026 22:45

bjester added 3 commits March 20, 2026 08:52

Migrate morango to uv for package management

665c52f

Update dependabot for uv

b9933f6

Migrate to prek for pre-commit hooks, and add docs

80a3f26

bjester force-pushed the uv-migration branch from a9374fc to 80a3f26 Compare March 20, 2026 15:53

bjester marked this pull request as ready for review March 20, 2026 16:04

marcellamaki reviewed Mar 20, 2026

View reviewed changes

rtibbles approved these changes Mar 20, 2026

View reviewed changes

rtibbles merged commit dfbc857 into learningequality:release-v0.9.x Mar 20, 2026
26 checks passed

bjester mentioned this pull request Mar 20, 2026

Documentation clarity updates #304

Merged

rtibbles mentioned this pull request Mar 26, 2026

Migrate to uv, setuptools-scm, prek, and ruff learningequality/kolibri#14457

Draft


		To start contributing to Morango, first make sure you [have `uv` installed](https://docs.astral.sh/uv/getting-started/installation/).

		Create a virtual environment, with at least python 3.9:

Uh oh!

Conversation

bjester commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

TODO

Reviewer guidance

AI usage

Uh oh!

marcellamaki left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

bjester Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rtibbles left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

bjester commented Mar 19, 2026 •

edited

Loading

bjester Mar 20, 2026 •

edited

Loading