chore: Move mypy to uv#6436
Merged
Merged
Conversation
Contributor
Codecov Results 📊❌ 13 failed | Total: 13 | Pass Rate: 0% | Execution Time: 6.82s ❌ Failed Tests
|
sl0thentr0py
force-pushed
the
neel/uv/mypy
branch
from
5f0edc9 to
16d3d77
Compare
sl0thentr0py
force-pushed
the
chore/migrate-to-tox-uv
branch
from
ad243c4 to
07280c2
Compare
sl0thentr0py
force-pushed
the
neel/uv/mypy
branch
from
16d3d77 to
a06be42
Compare
6 tasks
sl0thentr0py
force-pushed
the
neel/uv/mypy
branch
from
a06be42 to
5e18c7c
Compare
Member
Author
|
test failure is due to new redis 8 release for rq, will fix separately, ignore here |
alexander-alderman-webb
approved these changes
May 29, 2026
sentrivana
approved these changes
May 29, 2026
sl0thentr0py
merged commit 81acec3
into
chore/migrate-to-tox-uv
159 of 171 checks passed
sl0thentr0py
added a commit
that referenced
this pull request
May 29, 2026
## Description
* add `uv` and `tox-uv` to manage python envs and packages instead of
`pip`
* use `astral-sh/setup-uv` action in CI instead of `setup-python`,
top-level `uv` always uses `python3.14`
* except for 3.6 and 3.7, all python versions now go through `tox-uv`
* 3.6 and 3.7 have their own containers which `uv` picks up through
`UV_PYTHON_REFERENCE`
* the SDK is now installed as part of `deps` and not via `package` so
`uv` resolves all deps in a single pass, this was necessary since `uv`
resolution is stricter than `pip`
* `runtox.sh` also uses `uv run tox`
* some other pins were necessary to make CI pass
* pre-releases need a special `UV_PRERELEASE=ALL` for resolution to
work, we do not relax this throughout because `uv` then fetches
pre-releases for httpx and such breaking half the matrix
### Dev Flow Changes
No need for `asdf` or `pyenv` now if you were using it before, just use
`uv`, it will manage both `tox` and required python versions internally.
New commands:
- List tox envs: `uv run tox l`
- Integration tests: `uv run tox -e py3.14-{integration}-v{version}`
- Common tests: `uv run tox -e py3.14-common`
- Run specific test file:
`TESTPATH=tests/integrations/logging/test_logging.py uv run tox -e
py3.14-common`
- Run single test: `TESTPATH=tests/path/to/test_file.py uv run tox -e
py3.14-common -- -k "test_name"`
### TODO
* [ ] coverage (which is a mess anyway)
* [x] dev flow with `uv` as well - linters, top level tox, test file
generation all managed with `uv`
* [x] ruff: #6430
* [x] mypy: #6436
* [x] scripts/dist/apidocs/aws:
#6439
* [ ] dev flow docs (asdf) for python 3.6/3.7 since `uv` does not manage
those
---------
Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Neel Shah <neel.shah@sentry.io>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
keeping this in a separate dependency group since we install lots of random packages just for typing