Fix make.py updating uv.lock

[plaindocs]

Currently when you run ./make.py to generate the guidelines it modifies uv.lock instead of installing what is listed in the uv.lock, which results in a dirty git repo.

This might be related to the shebang in make.py:

#!/usr/bin/env -S uv run

Tagging @PLeVasseur

[MarcosBorgesPhD]

I worked on this today! There is an easy fix, but the challenge is ensuring compatibility with macOS/Linux/Windows.

Unfortunately, uv does not provide a way to enforce this via pyproject.toml, and adding --frozen to the shebang in make.py would only fix it for macOS and Linux users.

One solution is to harmonize how we run it, regardless of the platform. I see two paths:

Path 1 - Removing the shebang

This option is cross-platform and could "force" all contributors to run it via uv run --frozen make.py

For this, I need to update about 10 files that make reference to ./make.py. Actually, it is not necessary to remove the shebang, but I would remove it to prevent some inconsistencies with uv usage on CI vs local.

Path 2 - Updating the shebang in make.py

Just adding --frozen and updating the documentation keeping the mixed usage:

• For macOS and Linux: ./make.py
• For Windows: uv run --frozen make.py

---

For me, Path 1 is more radical, but more coherent for all platforms. Path 2 seems an easy fix but we need to keep different instructions per platform, and I’m not sure if the shebang with --frozen can impact CI that runs with uv --locked.

@plaindocs, @PLeVasseur, which path do you prefer?

[plaindocs]

I'd vote for option 1 here. Make the change now for longer term consistency. @PLeVasseur ?

Thanks for picking this up @MarcosBorgesPhD

[PLeVasseur]

Thanks for the inputs; I agree with @plaindocs on option 1.