Fix dependency: Python 3.11.9 breaks Dask #3963
Closed
Conversation
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
This was referenced Apr 13, 2024
This was referenced Apr 13, 2024
amotl
commented
Apr 13, 2024
Comment on lines
38
to
43
| # Parallel | ||
| dask>=2024.4.1 # Python 3.11.9 breaks Dask (https://github.com/dask/dask/issues/11038) | ||
| distributed>=2024.4.1 # Python 3.11.9 breaks Dask (https://github.com/dask/dask/issues/11038) | ||
| fugue | ||
| flask | ||
| Werkzeug>=2.2,<3.0 |
There was a problem hiding this comment.
Previous versions of Dask, which is pulled in transitively via Fugue through
pycaret[parallel], stopped working on Python 3.11.9, so that needs an update.
Of course, this should actually go into Fugue, but can also be fixed on both projects, depending on how fast this would converge into corresponding bugfix releases on the one project, or the other, and how convenient package maintainers would like to have the installation process for their users.
So, in the same spirit, that patch submits the same updates to the Fugue project.
Python 3.11.9 started to employ a different behaviour when raising `TypeError`s when reflecting docstrings, which leads to that error when importing `dask.dataframe`. TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object The solution is either to limit execution to Python <3.11.9, or to upgrade the `dask` and `distributed` packages to their most recent versions. Because PyCaret can't control on which Python versions it is used downstream, this patch uses the option to upgrade Dask. Because GitHub recently rolled out Python 3.11.9 on their runners, and other downstream users may also upgrade soon, it is advisable to release this update on behalf of a bugfix release.
27fc9aa to
e9ba61a
Compare
This was referenced Apr 13, 2024
|
Thanks for the PR, this will be included in #3968 |
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.
Problem
The recent release of Python 3.11.9 introduced an incompatibility with current versions of Dask.
Previous versions of Dask, which is pulled in transitively via Fugue through
pycaret[parallel], stopped working on Python 3.11.9, so that needs an update.Solution
In order to fix the problem without much efforts, this patch updates to a recent version of Dask>=2024.4.1, which includes a corresponding fix.
Evaluation
It is advisable to release this update on behalf of a bugfix release, so that downstream users will get this issue resolved quickly.
References