-
-
Notifications
You must be signed in to change notification settings - Fork 323
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
2.9.0 release notes #812
2.9.0 release notes #812
Conversation
Codecov Report
@@ Coverage Diff @@
## master #812 +/- ##
==========================================
- Coverage 99.94% 99.85% -0.09%
==========================================
Files 30 31 +1
Lines 10586 10613 +27
==========================================
+ Hits 10580 10598 +18
- Misses 6 15 +9
|
Hi, I just tested to build your 2_9_0 branch for a package for openSUSE Tumbleweed (which has fsspec 2021.7.0) and I still get
With #802 applied, the test_array tests pass, only test_create still fails. Could you try to include #802 into the release and fix the last one (here or in fsspec) please? |
I just found out, that fsspec/filesystem_spec#710 should fix the test_create failure. |
Hey @bnavigator. Thanks for giving this a try!
Agreed. Just waiting on the next release.
Do you agree #802 is only needed if one bumps fsspec to 2021.7.0? So, if fsspec is pinned to 2021.6 or earlier (or one installs from the mainline) that 2.9.0 currently works? |
Yes, but pinning to an earlier version is not an option for openSUSE Tumbleweed. Other packages already triggered the update of fsspec to 2021.7 causing the python-zarr package to fail. If you are not going to merge #802 into 2.9.0, I will have to apply the patch to our package manually. |
Agreed. Let's not include #802 just yet. I imagine an fsspec release will be along soon. Merging and moving forward with the release. |
For the record: |
With #773 now merged (:tada:), I'd like to get this out (today? Even thought it's a Friday?!) but it's a fairly big one. Any thoughts? Would anyone want an RC to test with?