Correct the uv script shebang in the standard and scripts - #292
Conversation
`#!/usr/bin/env -S uv run python` executes the interpreter directly and ignores the PEP 723 metadata block, so a directly invoked script fails at import time on machines without its dependencies preinstalled (verified empirically during the review of #291). Prescribe `#!/usr/bin/env -S uv run --script` in the scripting standard, explain why, and update `scripts/typos_rollout_check.py` to match.
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 46 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![codescene-access[bot]](https://avatars.githubusercontent.com/in/3755875?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
1 participant
Summary
This branch corrects the uv script shebang prescribed by docs/scripting-standards.md and used by scripts/typos_rollout_check.py. The previous form,
#!/usr/bin/env -S uv run python, executes the interpreter directly and ignores the PEP 723 metadata block, so a directly invoked script fails at import time wherever its dependencies are not preinstalled — verified empirically during the #291 review round. The standard now prescribes#!/usr/bin/env -S uv run --scriptand explains why.Validation
make markdownlint: 0 errors.uv run scripts/typos_rollout_check.py: exit 0 with the corrected shebang.--scriptmode.