open-telemetry / open-telemetry/opentelemetry-python-genai
Generate hermetic requirements.txt for oldest/latest from pyproject.toml as source of truth
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 63
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 175
Description
I think it would achieve the same, but hermetically, to generate
requirements.*.txtfromuv pip compile --resolution=...?We do this for a couple of packages in contrib (example opamp). It was difficult to do this across the board, and IIRC there was some bug in UV workspaces that made it difficult to do from
pyproject.tomlfiles.This LGTM but I'm happy to give it a shot in another PR. Would have fixed for example #410.
The idea is to use that instead of scripts introduced in #407. We can remove the boilerplate and tests won't fail depending on PyPI.
Originally posted by @aabmass in https://github.com/open-telemetry/opentelemetry-python-genai/pull/407#discussion_r3822588300
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 reading pyproject.toml and the scripts and tests introduced in PR #407. Check how uv pip compile can generate requirements.*.txt for oldest and latest resolutions from the project metadata, then verify the generated files keep tests independent of PyPI resolution changes and that the existing tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100