Fix ModuleNotFoundError in conda environments
#31
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
- Removed the (unnecessary) FORCE_CUDA flag from installation scripts. - Added an option to install extensions globally within conda environments to ensure compiled extensions are found. - Default behavior remains installing locally unless otherwise specified. - Clarified installation instructions to prevent ModuleNotFoundError when using a conda environment
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.
This PR supersedes my previous solution (PR #29) to issues #12 and #23 that incorrectly relied on
FORCE_CUDA. That approach masked the real issue, only working in my local setup due to additional dependencies that are not relevant in a clean environment.Key changes:
FORCE_CUDAworkaround (as FORCE_CUDA is never used in this project's setup files)ModuleNotFoundError)This solution properly addresses the module discovery issue while aligning with the project's existing setup procedure. Apologies for the confusion from my previous PR.