-
Notifications
You must be signed in to change notification settings - Fork 162
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
Add Python 3.11 to GHA #1090
Add Python 3.11 to GHA #1090
Conversation
@gliptak rebased onto dev so that all the branches are going into same branch prior to deployment to |
@taylorfturner consider setting
possible replacement is https://github.com/milesgranger/cramjam/tree/master/cramjam-python |
will rebase after #1091 merged |
@gliptak rebase onto |
@taylorfturner this might already be #1091 would have to be merged first |
* add downloads tile (capitalone#1085) * Replace snappy with cramjam * Delete test_no_snappy --------- Co-authored-by: Taylor Turner <taylorfturner@gmail.com>
https://github.com/capitalone/DataProfiler/actions/runs/8282560184/job/22663633408?pr=1090
|
@gliptak yeah I just started seeing this yesterday due to the package change by dask on the 12th. Haven't had the bandwidth to research why. I'd imagine a simple tag to not allow for this version would be a temporary fix to unblock |
https://github.com/capitalone/DataProfiler/actions/runs/8282934358/job/22664948501
dask/dask-expr#968 |
@taylorfturner corrected now there is a Keras(?) error https://github.com/capitalone/DataProfiler/actions/runs/8283138450/job/22665615645?pr=1090 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rebase onto dev
The advised solution is to upgrade to Dask version 2024.4.1. @taylorfturner am I to proceed with Dask bump as per above? https://github.com/capitalone/DataProfiler/actions/runs/9421219740/job/25954837467?pr=1090
|
Head branch was pushed to by a user without write access
https://github.com/capitalone/DataProfiler/actions/runs/9438503984/job/25995558872?pr=1090
|
.pre-commit-config.yaml
Outdated
python-snappy>=0.5.4, | ||
cramjam>=2.7.0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be reverted 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should match requirements.txt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
python-snappy>=0.7.1 supports Python 3.11 by switching over to cramjam and removing libsnappy-dev dependency (I contributed intake/python-snappy#130)
I will work dependencies in a minute
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we reverted these cramjam changes due to failing tests locally though in #1122.
- do we have to include cramjam + 3.11 in same pr?
- I'm game for the 3.11 add
- is the test suite running locally for you using
DATAPROFILER_SEED=0 python3 -m unittest discover -p "test*.py"
andtox -e py311
?
this is the above outstanding test fail python/cpython#87644
|
I see -- you are welcome to propose a fix for this as part of this PR (instead of a separate PR). If you get something operational, we can include this in the |
Head branch was pushed to by a user without write access
@taylorfturner I rewrote the test and it ran green locally. please review also let me know if separate bump PRs would work better (and guide on how you would like to split) |
.pre-commit-config.yaml
Outdated
python-snappy>=0.5.4, | ||
cramjam>=2.7.0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we reverted these cramjam changes due to failing tests locally though in #1122.
- do we have to include cramjam + 3.11 in same pr?
- I'm game for the 3.11 add
- is the test suite running locally for you using
DATAPROFILER_SEED=0 python3 -m unittest discover -p "test*.py"
andtox -e py311
?
@@ -55,7 +55,7 @@ repos: | |||
pyarrow>=1.0.1, | |||
chardet>=3.0.4, | |||
fastavro>=1.0.0.post1, | |||
python-snappy>=0.5.4, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why remove here? it is kept in requirements.txt
file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
synced with requirements
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome
Thanks, @gliptak !
|
Head branch was pushed to by a user without write access
python-snappy>=0.7.1 bump is required for Python 3.11 |
@@ -55,7 +55,7 @@ repos: | |||
pyarrow>=1.0.1, | |||
chardet>=3.0.4, | |||
fastavro>=1.0.0.post1, | |||
python-snappy>=0.5.4, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome
No description provided.