Adds support for uv managed projects, following the project's existing pattern of exporting a requirements file using the relevant project tool.
This does buck one-convention in this repo, in that it requires the user to have generated their own lock file, which is generally a best-practice when using one of these project management tools, and inspects for the existence of the uv.lock file as part of its check as to whether or not uv can be utilized with this plugin. This could be an issue for teams that are not otherwise committing their lock files to their repos and have automated deployments of their application in a CI/CD pipeline, although there exists trivial solutions to overcome that barrier.
Note: there is another issue, #830, which also asks for uv support in replacing pip, which this PR does not intend to include.
Resolves #849
Adds support for uv managed projects, following the project's existing pattern of exporting a requirements file using the relevant project tool.
This does buck one-convention in this repo, in that it requires the user to have generated their own lock file, which is generally a best-practice when using one of these project management tools, and inspects for the existence of the
uv.lockfile as part of its check as to whether or not uv can be utilized with this plugin. This could be an issue for teams that are not otherwise committing their lock files to their repos and have automated deployments of their application in a CI/CD pipeline, although there exists trivial solutions to overcome that barrier.Note: there is another issue, #830, which also asks for uv support in replacing pip, which this PR does not intend to include.