Skip to content

Show final targets for broken Python symlinks - #1326

Draft
zaniebot wants to merge 1 commit into
mainfrom
zb/resolve-broken-python-symlinks
Draft

zaniebot wants to merge 1 commit into
mainfrom
zb/resolve-broken-python-symlinks

Conversation

@zaniebot

Copy link
Copy Markdown
Collaborator

Broken interpreter warnings can report an intermediate link such as python instead of the missing executable. The warning reads only one symlink, so relative targets also lack the directory they are relative to.

Follow the interpreter's symlink chain when reporting broken project and tool environments, resolving each target relative to its containing directory. Keep uv's usual working-directory-relative path display, and omit the target if a cyclic, excessively long, or changed chain cannot be resolved. Interpreter selection and environment-recreation behavior are unchanged.

Refs astral-sh#21559.

@astral-automations-bot astral-automations-bot Bot added the area:error-messages Messaging when something goes wrong label Sep 10, 2026
@EliteTK EliteTK self-assigned this Sep 10, 2026
@zaniebot zaniebot added priority:3 Normal: useful features, documentation, usability, or routine efficiency improvements. size:2 Moderate: one subsystem with meaningful invariants, edge cases, or operational evidence to inspect. risk:1 Negligible risk of localized mistakes that are obvious and easy to correct. labels Sep 10, 2026
@astral-automations-bot
astral-automations-bot Bot force-pushed the zb/resolve-broken-python-symlinks branch from d24ebad to 6b2a32a Compare October 1, 2026 12:01
@codspeed

codspeed Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 54 untouched benchmarks
⏩ 35 skipped benchmarks1


Comparing zb/resolve-broken-python-symlinks (b6c5a34) with main (cea939e)

Open in CodSpeed

Footnotes

  1. 35 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

@astral-automations-bot
astral-automations-bot Bot force-pushed the zb/resolve-broken-python-symlinks branch 2 times, most recently from e6e4da0 to 6db7db5 Compare October 7, 2026 19:21
@astral-automations-bot
astral-automations-bot Bot force-pushed the zb/resolve-broken-python-symlinks branch from 6db7db5 to 8e85885 Compare October 7, 2026 22:07
@astral-automations-bot
astral-automations-bot Bot force-pushed the zb/resolve-broken-python-symlinks branch from 8e85885 to b377f2d Compare October 8, 2026 02:33
@astral-automations-bot
astral-automations-bot Bot force-pushed the zb/resolve-broken-python-symlinks branch from b377f2d to b6c5a34 Compare October 8, 2026 14:34

This branch was successfully deployed

1 active deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:error-messages Messaging when something goes wrong priority:3 Normal: useful features, documentation, usability, or routine efficiency improvements. risk:1 Negligible risk of localized mistakes that are obvious and easy to correct. size:2 Moderate: one subsystem with meaningful invariants, edge cases, or operational evidence to inspect.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants