pytest-dev / pytest-dev/pytest
Add an uv-managed Python to CI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
As demonstrated by #12888 and #13170, there is subtly different behavior regarding to input with uv-managed Pythons from python-build-standalone, as those use libedit instead of readline.
The existing tests in test_debugging.py mostly fail before #13176, so we would have easily caught #12888 earlier if we had a build job that runs with such a Python.
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 reviewing the existing CI build jobs and the tests in test_debugging.py, along with the related issues #12888, #13170, and #13176. Add a CI job using a Python managed by uv from python-build-standalone, then confirm the relevant tests pass and the job catches the differing libedit behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100