BLD: Avoid absolute pathnames in .pyx files #19123
Merged
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
to allow for reproducible builds even when (unneeded) .pyx files are installed and shipped in OS packages Fixes: scipy#19101 This patch was done while working on reproducible builds for openSUSE.
j-bowhay
added
the
Build issues
|
Seems like a harmless change to me, and all tests passing. Thank you @bmwiedemann |
rgommers
added
the
backport-candidate
8 tasks
tylerjereddy
removed
the
backport-candidate
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.
Reference issue
Closes #19101
What does this implement/fix?
Avoid absolute pathnames in
.pyxfilesto allow for reproducible builds
even when (unneeded) .pyx files are installed and shipped in OS packages.
Additional information
This patch was done while working on reproducible builds for openSUSE.