uv + uv.lock

[fabi1cazenave]

uv makes it so much easier to handle dependencies and venv. Amazing stuff.

@gagath any idea of what should be done to make it suitable for you as a Debian maintainer?

[gagath]

@fabi1cazenave We currently run the tests in autopkgtests by calling make test PYTHON3=$v for each supported python3 version in Debian to ease transitions: https://salsa.debian.org/python-team/packages/kalamine/-/blob/debian/latest/debian/tests/pytest?ref_type=heads

This change breaks make test by requiring uv, which we do not want to introduce as a dependency just to run tests. It also breaks the PYTHON3 variable. We could copy/paste the test lines into the autopkgtest script, but it is kind of a regression as we would need to watch for changes to the test target in the Makefile on every release.

From a packaging perspective, this PR is a regression.

[fabi1cazenave]

Hi @gagath, thanks for the quick reply.

I don’t expect Debian maintainers to depend on uv for Python packages, but I was wondering if there was an acceptable way to make it work for both workflows. Would it be okay if uv is used when available on the host, but not required ? T’hat’s what I think I’ve done in my latest commit.

I certainly don’t want to make it worse for packaging, but uv does make it easier for quick development tasks. Please let me know if the current proposal is okay. :-)

[fabi1cazenave]

Suddenly wondering whether this works on Windows or not.
@Geobert can you test this, please?

[Geobert]

will do this evening :)

[Geobert]

I don’t know much about uv so I rely on @gagath’s expertise ^^

[gagath]

Debian package and tests run OK with this uv branch. However new warnings are introduced because of the corpus thing. I will create a separate issue.

[gagath]

Here are the new issues related to corpus/ with the Debian packaging: #203

Again, not related to this uv PR that builds and tests fine with the debian packaging so good to merge for me.