-
Notifications
You must be signed in to change notification settings - Fork 482
build: migrate codespell and gitlint from pip to uvx #7829
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
+7
−31
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
uvx version specifier syntax @ == documentation💡 Result:
In uvx (alias of
uv tool run),@and==apply in different places:command@<version>(uvx shorthand) = exact tool version onlyUse this when the command name itself includes a pinned version, e.g.
uvx ruff@0.6.0 check. The docs note this form and that@is for an exact version (and@latestis also supported). [2]--from/--withuse standard Python dependency specifiers (PEP 508), e.g.==, ranges, extrasExamples:
uvx --from 'ruff==0.3.0' ruff checkuvx --from 'ruff>0.2.0,<0.3.0' ruff checkuvx --from 'mypy[faster-cache,reports]==1.13.0' mypy ...This is standard “dependency specifier” syntax (
name[extras] ==1.2.3,>=,<,!=, etc.). [2][3]CLI reference confirms
commandmay include<package>@<version>(for the command token), anduvxbehavior matchesuv tool run. [1]If you’re trying something like
--with "pkg@1.2.3", that typically won’t parse as a version pin—use--with "pkg==1.2.3"instead. (This mismatch is also discussed in uv’s issue tracker.) [4]Sources: uv CLI reference [1], uv “Using tools” guide [2], uv dependency specifiers (PEP 508) docs [3], GitHub issue discussion [4].
Fix uvx version specifier syntax.
uvx version pinning uses either
@for the direct command form (e.g.,uvx codespell@2.4.1) or PEP 508 specifiers with the--fromflag (e.g.,uvx --from 'codespell==2.4.1' codespell). The current form$(UVX) codespell==$(CODESPELL_VER)mixes both approaches and will not work. Use either$(UVX) codespell@$(CODESPELL_VER)or$(UVX) --from 'codespell==$(CODESPELL_VER)' codespell.🤖 Prompt for AI Agents