-
Notifications
You must be signed in to change notification settings - Fork 18
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
🩹 Disallow xarray 0.21.0 in setup.cfg #976
Conversation
Kudos, SonarCloud Quality Gate passed! |
Codecov Report
@@ Coverage Diff @@
## main #976 +/- ##
=====================================
Coverage 85.6% 85.6%
=====================================
Files 90 90
Lines 4883 4883
Branches 916 916
=====================================
Hits 4181 4181
Misses 552 552
Partials 150 150 Continue to review full report at Codecov.
|
Benchmark is done. Checkout the benchmark result page. Benchmark diff v0.5.1 vs. mainParametrized benchmark signatures: BenchmarkOptimize.time_optimize(index_dependent, grouped, weight)
Benchmark diff main vs. PRParametrized benchmark signatures: BenchmarkOptimize.time_optimize(index_dependent, grouped, weight)
|
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.
👍
Currently our ASV workflow fails since
xarray==0.21.0
had a mishap forgetting to addpackaging
as a dependency.Happens to the best of us, especially since
packaging
piggybacks onpytest
so you won't see this error in any test environment, and even in our docs something added it, so they pass.Anyway, to have our benchmarks work and go on with our stuff, let's just disallow this version until everything is sorted out.
If
xarray
decides to make a post-release, we can simply revert this change. If they rather choose to make a bugfix release it will stay in.Change summary
Checklist