-
Notifications
You must be signed in to change notification settings - Fork 419
ci: run py36 on the github actions #575
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
Conversation
|
Oh, I thought 3.6 was already supported (judging by the classifiers) but apparently it is not; #522. This might be a dead cause |
|
You would need to change |
Yes, I am aware. I thought it was the |
|
Indeed, it seems a little unfortunate. The selectors are certainly not authoritative, but This could have been a more public discussion. If py36 support is easy, I am not opposed to continuing with it. |
890d2cd to
146de63
Compare
|
Apparently all tests pass, though pyarrow seems to be a bit problematic when installed in <1, is there anything I should be aware when bumping it to 1>=? |
|
Do you mean pyarrow -> v>1.0? That should be OK. The HDFS implementation is slated to be dropped, but not yet. |
|
yep |
|
OK, thanks for doing this - let's keep py36 alive a little longer! |
|
Thanks @martindurant! |
3.6 has reached the EOL. fsspec (along with pydata) dropped support for it early 2021, but we brought it back for dvc in #575.
3.6 has reached the EOL. fsspec (along with pydata) dropped support for it early 2021, but we brought it back for dvc in #575.
3.6 has reached the EOL. fsspec (along with pydata) dropped support for it early 2021, but we brought it back for dvc in #575.
No description provided.