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?

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.

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

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.

I'm ready.

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

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 👀

Also curious aws xray propagator test failures.

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

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?

I dropped xray from the list of packages. It seems the problem is that on the tests, we try to install a package that is listed in the pyproject, but on the pyproject it references a commit, and in the tox it references a version.

I asked on their discord to see if I can do something about it.

But the test suite has their own virtual environments, so it's all good.

I dropped xray from the list of packages. It seems the problem is that on the tests, we try to install a package that is listed in the pyproject, but on the pyproject it references a commit, and in the tox it references a version.

I asked on their discord to see if I can do something about it.

But the test suite has their own virtual environments, so it's all good.

Just a note: The same will happen for all packages that are tested using pinned released versions of api/sdk in test requirements e.g., gen-ai stuff

🥳