fix(python): Fix the build dependency failure that occurred in pyfory - #2596
Merged
Conversation
chaokunyang
approved these changes
Sep 9, 2025
pandalee99
changed the title
Collaborator
|
@pandalee99 This PR needs be reverted, it cause pip install executed |
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
2 participants
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.
Why?
When I repeatedly perform
pip install -v e., I encounter the problem of not being able to find pyarrow. This issue is very similar to #1645. However, as long as I performbazel clean --expunge, the problem can be solved. I think this might be dependency pollution caused by the virtual environment.What does this PR do?
Related issues
Does this PR introduce any user-facing change?
relate #2595
Benchmark