Skip to content
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

Convert dask upper-binding into exclusion #31329

Merged
merged 1 commit into from
May 16, 2023

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented May 16, 2023

As dask/dask#10279 has been solved and Dask tests should no longer generate a PATH side-effect, we should turn the upper-binding into exclusion, to make sure that we upgrade to newer Dask version when it is released.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

As dask/dask#10279 has been solved and
Dask tests should no longer generate a PATH side-effect, we
should turn the upper-binding into exclusion, to make sure that
we upgrade to newer Dask version when it is released.
@potiuk potiuk merged commit 45f1fda into apache:main May 16, 2023
@potiuk potiuk deleted the convert-upper-bound-into-exclusion branch May 16, 2023 21:02
@eladkal eladkal added this to the Airflow 2.6.2 milestone Jun 8, 2023
@eladkal eladkal added the type:misc/internal Changelog: Misc changes that should appear in change log label Jun 8, 2023
eladkal pushed a commit that referenced this pull request Jun 8, 2023
As dask/dask#10279 has been solved and
Dask tests should no longer generate a PATH side-effect, we
should turn the upper-binding into exclusion, to make sure that
we upgrade to newer Dask version when it is released.

(cherry picked from commit 45f1fda)
eladkal pushed a commit that referenced this pull request Jun 9, 2023
As dask/dask#10279 has been solved and
Dask tests should no longer generate a PATH side-effect, we
should turn the upper-binding into exclusion, to make sure that
we upgrade to newer Dask version when it is released.

(cherry picked from commit 45f1fda)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:misc/internal Changelog: Misc changes that should appear in change log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants