Fix Windows ModuleNotFoundError on unit testing workflow#57
Merged
Conversation
- Moved 'sys.path.append' lines to the start of 'main.py' - Ensured correct directory access for unit tests in Windows environment
kagami-l
approved these changes
Jan 29, 2024
This file contains hidden or 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
2 participants
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.
This pull request addresses the issue where Windows users experienced a
ModuleNotFoundErrorwhen running the unit testing workflow. The problem was due to an incorrect file path.Changes:
sys.path.appendto ensure it occurs earlier inmain.pyBy moving the path append to an earlier phase and adjusting path access, it should now properly locate the needed modules on the Windows platform.
This resolves the issue reported in devchat-ai/devchat#226.