chore: run tests with uv

[tokoko]

switches to using uv lockfile to run tests to make ci environment more reproducible.

[nielspardon]

@tokoko what do you think about updating the https://github.com/substrait-io/substrait-python/blob/main/CONTRIBUTING.md file? that feels a bit out of sync to me if we are using uv I guess we don't need to tell people to use conda or am I missing something?

[tokoko]

I guess we can do that, yeah. I've personally never used that conda environment, I'm fairly sure no one else is using it either.

[mbwhite]

@tokoko @nielspardon using uv would be a good idea I think for dependencies as well. To get a working local environment I was able to use uv successfully.

Happy to help here - testing or updating..

[nielspardon]

it looks like the issue is caused by a protobuf version incompatibility. the google.protobuf.any introduced by @mbwhite seems to only exist in more recent versions of protobuf but not in version 3.20.1 which uv seems to pick currently.

the older version only has google.protobuf.any_pb2

[mbwhite]

Checked what I've got locally in uv.lock and that is protobuf 3.20.1 - and the tests pass. And the build originally past; the virtual environments are very confusing.

Does the pyproject.toml need to have the dependencies added?

Update: Cloning this PR and running (python3.12) there aren't any issues with the tests... 🤷

It's the generation of the protos.. ah!

[nielspardon]

I have a fix. will provide a separate PR

[nielspardon]

this should fix it: #111

[tokoko]

I fixed the tests in here as well. We can avoid bumping lower bound unnecessarily, especially when it's just test code.

[nielspardon]

I fixed the tests in here as well. We can avoid bumping lower bound unnecessarily, especially when it's just test code.

great, that should also work

[nielspardon]

LGTM, just two typos I found in the markdown file