feat(install): use uv

[ntarocco]

No description provided.

[ntarocco]

To be ported to the production branch too.

[utnapischtim]

why do you want to add the uv.lock file?

[ntarocco]

why do you want to add the uv.lock file?

For this repo is not very interesting indeed, I can remove it if you prefer.

[Samk13]

why do you want to add the uv.lock file?

if you delete uv.lock, the uv sync --locked in the CI cannot work because there's no lock to check. We need to remove the flag as well in that case.

[ntarocco]

why do you want to add the uv.lock file?

if you delete uv.lock, the uv sync --locked in the CI cannot work because there's no lock to check. We need to remove the flag as well in that case.

Right, however we can decide if it is really needed for this case. Normally you want a lock file when you need to install in your env the same exact dependencies. For the doc, is it not that crucial, and I doubt that locally people will update it when committing the new change.
I would be in favor of removing it for the above considerations. WDYT? @utnapischtim @Samk13

[fenekku]

Yup that works. (I've also been using uv for it locally for a long time but via uv pip install -r requirements.txt). Thanks!

[fenekku]

It seemed strange to me to need a pyproject.toml at first (I am used to uv run --no-project ... and this isn't really a package), but if we do want to use uv sync and skip the step of manually creating a virtualenv, it makes sense.

(we'll see about that python version in the future hahaha)

[mfenner]

When running this, I get these messages:

INFO    -  The following pages exist in the docs directory, but are not included in the "nav" configuration:
             - maintenance/architecture/faq.md
             - maintenance/internals/extensions.md
             - maintenance/internals/frontend.md
             - maintenance/internals/naming.md
             - operate/customize/requests.md
             - releases/vNext/upgrade-vNext.md
             - releases/vNext/version-vNext.md
INFO    -  Doc file 'releases/vNext/upgrade-vNext.md' contains a link '#opensearch-version', but there is no such anchor on this page.

I assume this is intentional and not related to the migration to uv.

[fenekku]

I don't think it's intentional but it is not related to uv :). Just a link to fix in that page.