MNT: add first-class uv support for install and development - #393
Draft
syedhamidali wants to merge 1 commit into
Draft
MNT: add first-class uv support for install and development#393syedhamidali wants to merge 1 commit into
syedhamidali wants to merge 1 commit into
Conversation
syedhamidali
force-pushed
the
feat/uv-installation
branch
2 times, most recently
from
July 19, 2026 09:45
4196eb6 to
c2441c2
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #393 +/- ##
=======================================
Coverage 94.23% 94.23%
=======================================
Files 29 29
Lines 6452 6452
=======================================
Hits 6080 6080
Misses 372 372
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
syedhamidali
force-pushed
the
feat/uv-installation
branch
from
August 14, 2026 14:54
c2441c2 to
2b82a1f
Compare
- Commit uv.lock for reproducible dev environments (`uv sync --extra dev`) - Document uv install/dev workflows in installation.md and CONTRIBUTING.md - Run the CI lint job via astral-sh/setup-uv (pinned) instead of pip The conda/micromamba test matrix is kept as-is, since the scientific binary stack (netCDF4, h5py, xarray-dev) is still resolved via conda-forge.
syedhamidali
force-pushed
the
feat/uv-installation
branch
from
August 14, 2026 14:56
2b82a1f to
d121a14
Compare
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
1 participant
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.
Summary
Adds first-class uv support for installing and developing xradar:
uv.lockfor reproducible dev environments (uv sync --extra dev)installation.mdandCONTRIBUTING.mdastral-sh/setup-uv(SHA-pinned) instead of pipScope
This is a measured first step toward the CI tooling discussion in #381 — it adds uv where it's a clean win (install, dev env, lint) while keeping the conda/micromamba test matrix as-is, since the scientific binary stack (netCDF4, h5py, xarray-dev) is still resolved via conda-forge. Happy to extend uv further, or move toward pixi, depending on where #381 lands.
Notes
pyproject.tomlis unchanged — uv reads the existing project metadata and the dynamicdevextra directly.uv sync --extra devbuilds a working env (xradar imports, tests pass).