Handle bad paths in sys.path
#2383
Merged
Conversation
This file contains 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
lostmsu
force-pushed
the
bugs/sys.path-invalid
branch
3 times, most recently
from
3b2958b
to
eef9619
Compare
lostmsu
force-pushed
the
bugs/sys.path-invalid
branch
from
eef9619
to
eb61851
Compare
filmor
approved these changes
May 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this implement/fix? Explain your changes.
User can add arbitrary strings to
sys.path. When we probe for assemblies insys.paththe ones that were not valid paths caused the probing to fail, never reaching the valid ones that actually had the desired assembly.This change handles these cases by generating a warning and continuing to probe in other directories.
Does this close any currently open issues?
fixes #2376
Checklist
Check all those that are applicable and complete.
CHANGELOG