-
Notifications
You must be signed in to change notification settings - Fork 159
Fix discovery for trampoline files #230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
recursive-include cuda/ *.pyx *.pxd | ||
# at least with setuptools 75.0.0 this folder was added erroneously | ||
# to the payload, causing file copying to the build environment failed | ||
exclude cuda/bindings | ||
exclude cuda/bindings cuda?bindings | ||
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be clear this is NOT a bug fix (the one-liner change below is), just a really unpleasant workaround for presumably two (2) potentially correlated setuptools bugs. Many engineering hours are wasted only to find this WAR in order to accommodate for both Linux and Windows. Yes, we need both; can't just pick either of them.
What happened is (paraphrasing @vzhurba01's comment from the internal discussion): We need to fix
pyproject.toml
to find all extension modules starting withcuda
(which was missed in the hot fix 12.6.2/11.8.5), so that all modules' Cython sources can be included in the package.However, once we do this we see a very strange error on both platforms at build time
which suggests that setuptools tries to copy this folder as a regular file. This is likely the first bug.
What's happening here is that as part of
egg_info
source file discovery, it fetches files directly frombuild_ext
. Files found use a mix of Linux and Windows path separators (/
and\\
, respectively). One of the paths found iscuda/bindings
(which should not have happened in the first place).To work it around, we rely on
MANIFEST.in
letting us specify which path/file to exclude, and so we addedexclude cuda/bindings
when we worked on the layout change #137. Since setuptools' docs clearly stated thatthis should have been a cross-platform WAR.
The next bug that bites us is that
egg_info
tries to be "smart" by converting all Linux separators to Windows, therefore ourexclude
only applies tocuda\\bindings
and thus failing the Windows build later on. This is the second bug, and the WAR is to rely on this documented little trick (same setuptools page as linked above):There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thomasjpfan in case you're still interested in knowing what happened 🙂