Repository navigation
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.
Windows wheel builds failed because the embedded libdiffpy sources assumed POSIX APIs and contained declarations incompatible with modern MSVC. Generate compatible headers and native Windows runtime path discovery in the build directory, enable mathematical constants for the core and extension, and explicitly resolve nanobind item handles when restoring calculator pickle tuples.
Runtime tables remain relative to the installed extension, with DIFFPYRUNTIME taking precedence. The pinned libdiffpy revision, archive checksum, source overrides, existing tests, and CI workflows are unchanged.
Validation of the unchanged build/runtime implementation on f03621b: