fix(examples) Remove numpy specification in vertical-fl
#4724
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
… dependency conflict
TheVidz
requested review from
jafermarq,
tanertopal and
danieljanes
as code owners
jafermarq
changed the title
numpy specification in vertical-fl to solve conflictnumpy specification in vertical-fl
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.
… dependency conflict
Issue
This PR is to fix issue #4722
Description
Removes the
numpyspecification inpyproject.toml. As this was causing a dependency conflict. This issue arises because until recently flower had to use numpy<2.0 but this was removed a couple of releases ago.Related issues/PRs
Proposal
Explanation
Checklist
#contributions)Any other comments?