open-telemetry / open-telemetry/opentelemetry-python-contrib
Improve UV local dev setup to generate the list of sources
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
I think it can be an improvement not to get the list of packages out-of-date. Maybe we can have the `uv.toml` file generated from a jinja2 template. Was that the original idea?
Originally posted by @emdneto in https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3124#discussion_r1916991597
The dependencies and uv.tool.sources are repetitive and error prone, plus they require updating when new packages are added. We could generate it from globs ideally.
Also looks like UV may support this directly in the future astral-sh/uv#7143
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing uv.toml and the repeated dependencies and uv.tool.sources entries. Determine how a Jinja2 template or package globs could generate the source list, and check the current local development setup for validation. Done means newly added packages no longer require duplicating entries while the generated configuration remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100