Fix incorrect FileNotFoundError in load_nox_module #571
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
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.
Closes #566
This PR fixes the incorrect raising of
FileNotFoundErrorwhen loading the nox module if it contains module-level file operations on non-existing files.I've moved the
_load_and_exec_nox_modulepast theFileNotFoundErrorandOSErrorexception checks and changed the exceptions it could raise into assert statements as they were all covering internal importlib exceptions that are pretty much fatal.See conversation on issue from this comment onwards for context: #566 (comment)