Skip to content

gh-128670: Use the pyvenv.cfg home location in getpath when the default executable points to the same realpath as the running executable - #128913

Open
pelson wants to merge 4 commits into
python:mainfrom
pelson:fix/venv-platbase
Open

gh-128670: Use the pyvenv.cfg home location in getpath when the default executable points to the same realpath as the running executable#128913
pelson wants to merge 4 commits into
python:mainfrom
pelson:fix/venv-platbase

Conversation

@pelson

@pelsonpelson commented Jan 16, 2025

Copy link
Copy Markdown
Contributor

Follows on from the issues raised in #128670 and #106045. It should be considered as an alternative to #115237.

…same file as the executable being run once symlinks are resolved
…ine if it is a good idea to use the home value for base_executable determination
@pelson

Copy link
Copy Markdown
ContributorAuthor

I can't currently reproduce the failing tests locally. Any advice on doing so?

@pelson

Copy link
Copy Markdown
ContributorAuthor

I'm wondering if #129137 is fixing the pipeline failure for this case too.

@github-actions

Copy link
Copy Markdown

This PR is stale because it has been open for 30 days with no activity.

@github-actionsgithub-actionsBot added the stale Stale PR or inactive for long period of time. label Apr 21, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting reviewstaleStale PR or inactive for long period of time.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@pelson