You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tomvothecoder, @chengzhuzhang, @whannah1, I would prefer not to delay Unified testing for this. Could we consider constraining scipy<1.15 in e3sm_diags for the time being while you all work this out?
A second question: do you all have a strategy for detecting deprecation warnings like this (e.g. as outputs from your testing) so they can be addressed before they become a last-minute problem? I know tests spit out a lot of deprecation warnings and sometimes they're related to other tools (like xarray) but they can sometimes be a helpful indication that something like this is coming.
What happened?
Per https://docs.scipy.org/doc/scipy-1.12.0/reference/generated/scipy.signal.cwt.html:
What did you expect to happen? Are there are possible answers you came across?
dev.yml
,ci.yml
andpyproject.toml
scipy.signal.cwt
with PyWaveletse3sm_diags/e3sm_diags/driver/qbo_driver.py
Lines 410 to 421 in df10271
Minimal Complete Verifiable Example (MVCE)
No response
Relevant log output
Anything else we need to know?
Found in PR #907, where integration tests are breaking due to this issue.
Related SciPy docs:
Related PyWavelets docs:
Environment
Latest
e3sm_diags
onmain
scipy=1.15.1
The text was updated successfully, but these errors were encountered: