Fix Python stub installation with sanitizers enabled - #526
Open
jeongseok-meta wants to merge 1 commit into
Open
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
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.
Motivation
Sanitizer builds deliberately skip Python stub generation, but the install rules still list the absent
.pyiandpy.typedfiles, socmake --installfails. Those builds still need the empty runtime module files used bydrjit,drjit.llvm, anddrjit.auto.This keeps the existing sanitizer behavior without adding a user-facing option to disable stubs.
This is an independent upstream-only cleanup with no corresponding conda-forge patch, so it does not require a downstream patch-removal follow-up. The clean-output-directory issue is handled separately in #525.
Changes
drjit.autoruntime modules for sanitizer builds.Validation
drjit/__init__.pyi.drjit,drjit.llvm, anddrjit.autoimport withlibasanpreloaded.drjit-auto-stub, and verified the generated install manifest has no.pyiorpy.typedentries.drjit/autobuild directory to isolate the separate directory-creation issue in #525); verified all 15 existing stub/marker files and the same imports.git diff --check