Handle wheel installs correctly#16
Merged
AmaranthineCodices merged 2 commits intomainfrom Sep 15, 2025
Merged
Conversation
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
1 participant
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.
When installing MAX as a wheel, we don't ship a modular.cfg file we can use to launch CLI tools. This is mostly worked around on the packaging end, where CLI tools are wrapped to set the necessary environment variables directly, but we have to make some adjustments to the SDK loading code to work with the different structure.
There is one caveat: debugging the current Mojo file is not supported, because we can't launch the wrapped
mojoexecutable under LLDB. We can handle this better in the future, but for now you just get an error.