Repository navigation
TEST-#7705: Cap fuzzydata<0.1 in dev requirements. - #7706
Open
suhailrehman wants to merge 2 commits into
Open
suhailrehman wants to merge 2 commits into
suhailrehman wants to merge 2 commits into
Conversation
The fuzzydata pin has no upper bound, so dev environments resolve to the latest release on PyPI. fuzzydata 0.1.0 changes the workflow generator API and the output layout that modin/tests/experimental/test_fuzzydata.py asserts on, which would break the fuzzy CI job on the next PR touching modin/** once 0.1.0 is published. Cap the requirement at <0.1 in both requirements-dev.txt and environment-dev.yml. The pin can be raised once the integration is updated for the new API; I maintain fuzzydata and am happy to send that follow-up. Signed-off-by: Suhail Rehman <suhailrehman@gmail.com>
suhailrehman
requested review from
a team,
RehanSD,
YarShev,
anmyachev,
dchigarev,
devin-petersohn,
mvashishtha and
vnlitvinov
as code owners
August 27, 2026 04:38
The fuzzydata pin has no upper bound, so dev environments resolve to the latest release on PyPI. fuzzydata 0.1.0 changes the workflow generator API and the output layout that modin/tests/experimental/test_fuzzydata.py asserts on, which would break the fuzzy CI job on the next PR touching modin/** once 0.1.0 is published. Cap the requirement at <0.1 in both requirements-dev.txt and environment-dev.yml. The pin can be raised once the integration is updated for the new API; I maintain fuzzydata and am happy to send that follow-up. Signed-off-by: Suhail Rehman <suhailrehman@gmail.com>
This branch has not been deployed
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.
The fuzzydata pin has no upper bound, so dev environments resolve to the latest release on PyPI. fuzzydata 0.1.0 changes the workflow generator API and the output layout that
modin/tests/experimental/test_fuzzydata.py asserts on, which would break the fuzzy CI job on the next PR touching modin/** once 0.1.0 is published.
Cap the requirement at <0.1 in both requirements-dev.txt and environment-dev.yml. The pin can be raised once the integration is updated for the new API; I maintain fuzzydata and am happy to send that follow-up.
What do these changes do?
flake8 modin/ asv_bench/benchmarks scripts/doc_checker.pyblack --check modin/ asv_bench/benchmarks scripts/doc_checker.pygit commit -sdocs/development/architecture.rstis up-to-date