Implemented first version of uv executor

[AKuederle]

Description of changes

This PR implements a uv-executor that uses uv run to execute tasks against the virtual env. The advantage over executing uv projects with the normal venv executor is, that uv run will automatically update and sync packages and is hence, recommended over activating the venv manually when working with uv.

@nat-n This is a first version, and I just wanted to get your feedback, if this is something you would be interested in merging.

See also #257

Pre-merge Checklist

• New features (if any) are covered by new feature tests
• New features (if any) are documented
• Bug fixes (if any) are accompanied by a test (if not too complicated to do so)
• poe check executed successfully
• This PR targets the development branch for code changes or main if only documentation is updated

[nat-n]

Do you think it's worth declaring a dependency here to exercise the integration more fully?

If yes there's a locally vendored package you can use like

poethepoet/tests/fixtures/poetry_plugin_project/pyproject.toml

Line 11 in 9997e87

cowpy = { path = "../packages/cowpy-1.1.5-py3-none-any.whl" }

[nat-n]

Hey @AKuederle, this looks pretty good. Thanks for working on it!

In the poetry executor I prefer using the venv directly, mostly to avoid the latency of the poetry CLI, but I guess that's not such an issue with uv :)

[AKuederle]

Yes I think the entire idea behind uv run is that running the additional checks is so fast, that it does not matter.
We might need to add a fallback (as I don't know what happens in cases where you don't have internet).

Regarding tests: I wasn't sure what tests to add. Based on my understanding, by adding a new project folder it should be included in the fixture. But I am not sure if this is sufficient. I also got some failing tests that did not seem to be related to my changes.

Could you provide some pointers, what I should update add, for you to consider merging this?

[nat-n]

I'm curious how you would make an offline fallback work (if it's needed)?

I'm afraid the testing setup isn't quite that clever. Given the fixture project you created you'll need a test using run_poe_subproc, for example: run_poe_subproc("test-package-exec-version", project="uv").

Most tests work the same way, you can look here for example: https://github.com/nat-n/poethepoet/blob/main/tests/test_executors.py You can either extend that test module or create a new more specific one.

If a test takes more than a couple of seconds to run (for example due to needed to setup the venv for the uv project) then it should be marked with @pytest.mark.slow, and if it requires the uv executable to be present to pass then it should be marked with @pytest.mark.skipif(not shutil.which("uv"), reason="No uv available")

I see a test failing due to a recent unreleased change I made. I pushed a fix to the development branch so you can rebase to get it.