Summary

Extract the Python 3.14-compatible venv executable-symlink behavior from #8954 (43065e79ddc46eafeca58cb39398ac007b5d25f7), without copying its broader custom metadata traversal.

When pyvenv.cfg supplies a home directory, follow final-component executable symlinks before falling back to home/<invoked name>. Preserve directory aliases, copied-executable fallback, non-venv invocation paths, Windows behavior, and existing launcher-override precedence.

The resolver follows CPython 3.14.7's getpath helper, including its bounded traversal, rather than using filesystem canonicalization, which would incorrectly resolve directory aliases. The selection contract is in getpath.py.

Validation

• Independent source review caught and corrected directory-alias handling and the macOS-framework limitation in the initial test design before publication.
• Exact CPython 3.14.7 and the native final head pass the complete existing sys snippet, including nine bounded scenarios: absolute/relative/chained links, both config locations, non-venv preservation, copied fallback, directory aliases, double-leading slash, and Linux launcher override.
• Both dedicated snippet pytest entries pass under Python 3.14.7. The original generic local runner used Python 3.12, whose -S prefix behavior differs; validation was moved to the correct reference version without weakening assertions.
• Normal hooks, VM Clippy, and separately configured CAPI Clippy pass with -D warnings.

All new assertions are Python-side. Children only print sys attributes, run with -B -S and timeouts, and execute the trusted interpreter or its copy inside owned temporary directories. No package installation, configuration-provided executable, dangling/cyclic launch, or root-path probe is part of the tests.

Boundaries

The local character-count rule follows RustPython's existing UTF-8/surrogateescape filesystem contract; arbitrary non-UTF-8 CPython locale parity is not claimed. Root-level edge behavior was source-reviewed only. WASI/Emscripten are excluded from new runtime coverage; non-Linux native execution remains unverified.

No cfg parser, custom base-executable/executable metadata, PYTHONHOME handling, shared path converter, or canonical test assertion/marker is changed. Canonical test_getpath.py is absent from this checkout; no canonical-suite pass is claimed. Hosted CI remains required.

Summary by CodeRabbit

• Bug Fixes
  • Virtual environments now correctly identify the executable behind absolute, relative, and chained symlinks, improving executable path reporting when launching through a symlink.
  • When a virtual environment specifies a home directory, a resolved executable path is used when available; otherwise, the existing fallback is retained.
  • Executable paths remain unchanged for non-virtual-environment launches and copied executables.

macOS framework reference correction

Follow-up f29bb73 corrects the new test fixture's expectations for the installed macOS framework launcher. The launcher recreates __PYVENV_LAUNCHER__, presets the framework base, and canonicalizes the invocation directory (launcher source, getpath precedence). The fixture now combines the configured framework feature with exact installed-launcher file identity; direct embedded-app binaries keep the ordinary path expectations. All cases and exact assertions remain; no implementation-name guard or production change is added.

The corrected full snippet passes native RustPython and both CPython 3.14.7/3.14.8 references on Linux; the reference/native pytest harness also passes. Independent source review and normal hooks passed. Production files are identical to 68ea941, whose native binary was reused for this test-only validation. Actual macOS framework validation requires the new hosted run; it has not been reproduced locally. An arbitrary copied framework stub as the original parent interpreter remains outside this fixture's pre-existing scope.