Use UV to install all needed packages locally

[Kludex]

This is specifically to have a single virtual environment with all dependencies to make it easier to develop here.

[emdneto]

Loved this. I would say other than speed-up local development, this paves the way to adopt uv in opentelemetry-python.

I think it will be necessary to add some instructions on how to use that. But just a note for reviewers:

With a simple command like uv sync you can have all packages from the project installed locally. If you want to install only one package you can run: uv sync --package opentelemetry-instrumentation-sqlalchemy for example.

[xrmx]

Loved this. I would say other than speed-up local development, this paves the way to adopt uv in opentelemetry-python.

I think it will be necessary to add some instructions on how to use that. But just a note for reviewers:

With a simple command like uv sync you can have all packages from the project installed locally. If you want to install only one package you can run: uv sync --package opentelemetry-instrumentation-sqlalchemy for example.

Sure but aren't we adding another source of dependabot warnings? I'm fine on adding the metadata to the pyproject for people using uv but isn't this duplicating what we use tox for?

[Kludex]

Sure but aren't we adding another source of dependabot warnings?

Unfortunately/Fortunately, Dependabot doesn't see the uv.lock yet.

I'm fine on adding the metadata to the pyproject for people using uv but isn't this duplicating what we use tox for?

Not really. The idea here is to have a single virtual environment that can be used by the IDE, and to simplify local development (running some scripts locally to test some integrations, etc). The tox is used to run the tests with multiple different environments, it doesn't really create this virtual environment.

[idan-rahamim-lendbuzz]

Is it possible that opentelemetry-bootstrap --action=install would install with UV/Poetry instead of pip?

[Kludex]

Is it possible that opentelemetry-bootstrap --action=install would install with UV/Poetry instead of pip?

This is not related with this PR, please create an issue.

[aabmass]

I think you may need to regenerate the lockfile, it fails for me unless i regenerate with

      AttributeError: module 'falcon' has no attribute '__version__'

      hint: This usually indicates a problem with the package or the build environment.
  help: `falcon` (v3.1.1) was included because `opentelemetry-python-contrib` (v0.0.0) depends on `opentelemetry-instrumentation-falcon[instruments]`
        (v0.51b0.dev0) which depends on `falcon`

[Kludex]

What fails? Which command did you use?

[aabmass]

uv sync

[Kludex]

That updates the lock file.

I'll write some notes on how to use it.

[Kludex]

You'd need to do uv sync --frozen, which doesn't update the lockfile.

[emdneto]

uv sync --frozen is failing for me too

[emdneto]

@Kludex could you please write a guide on how people can use this setup? Maybe a small section in CONTRIBUTING.md is enough.

[codefromthecrypt]

Looking forward to this. I have some awkward instructions on how to install things which I hope uv makes easier. Each time I use uv/uvx it seems quicker and simpler than before, so 👍

[Kludex]

I'm ready.

[xrmx]

Looks like the uv.lock is confusing ruff? Also curious aws xray propagator test failures.

[Kludex]

Looks like the uv.lock is confusing ruff? Also curious aws xray propagator test failures.

No...

[testenv:ruff]
basepython: python3
deps =
  -c {toxinidir}/dev-requirements.txt
  pre-commit
commands =
  pre-commit run --color=always --all-files {posargs}

Calling the test ruff but running pre-commit doesn't help 👀

[Kludex]

Also curious aws xray propagator test failures.

It seems it's looking to the uv.lock.

[Kludex]

Also curious aws xray propagator test failures.

It seems it's looking to the uv.lock.

@emdneto we talked about this at some point. Do you remember why?

[emdneto]

@Kludex According to documentation:

Within a workspace, dependencies on workspace members are facilitated via tool.uv.sources,

so since we have tests pointing to pinned versions of API (as example 1.16 for awsxray propagator) uv is trying to install it using the source at Git instead of PyPI and this version doesn't exist in ref main. I think this is happening because tox-uv is running based on what is defined at pyproject.toml

[emdneto]

Same will happen for all packages that are tested using pinned released versions of api/sdk in test requirements (example: gen-ai stuff)

[emdneto]

Instead of workspaces maybe we can have this for sources:

opentelemetry-propagator-aws-xray = { path = "./propagator/opentelemetry-propagator-aws-xray", editable = true }
opentelemetry-propagator-ot-trace = { path = "./propagator/opentelemetry-propagator-ot-trace", editable = true  }