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

python 2.7 env with old zarr #226

Merged
merged 3 commits into from
Oct 12, 2020
Merged

python 2.7 env with old zarr #226

merged 3 commits into from
Oct 12, 2020

Conversation

timothyas
Copy link
Member

Current python 2.7 tests break because of zarr, which has not supported python 2 since version 2.3.2. This PR specifies zarr<=2.3.2 in the ci/environment file.

@rabernat
Copy link
Member

rabernat commented Oct 7, 2020

Thanks Tim! Can we just drop python 2 going forward for xmitgcm? Or maybe make a release now and then drop on the next release?

@timothyas
Copy link
Member Author

Hmm, I'm not sure what is best so I'll leave that to you. Dropping python 2 would be fine with me, would that just involve removing python 2.7 tests and dropping it from setup? Happy to move forward with either.

@rabernat
Copy link
Member

Let's merge this, release 0.5.0, and then drop python 3 for 0.6.

@rabernat rabernat merged commit a5d2979 into MITgcm:master Oct 12, 2020
@timothyas timothyas deleted the zarr_py27 branch October 28, 2020 16:54
fraserwg pushed a commit to fraserwg/xmitgcm that referenced this pull request Nov 23, 2021
* attempt to fix py27 with old zarr

* alternate soln with setup

* didn't work, back to first soln
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants