Tracking issue: Caiman and numpy 2.0
pgunn opened this issue · 2 comments
numpy 2.0 has release candidates, so a full release is just around the corner.
Right now caiman pins numpy at <2.0.
There's no need to try to test/fix our code before the 2.0 release, but it should be on our radar to adjust our code for 2.0 in the mid-term. Depending on the issues that come up we may:
A) Be able to get along with both versions, or
B) Need to treat this as a gate, doing a minimum version pin after the adjustments
I see both as acceptable, although the former is preferable because we'd be less all-elbows with other packages and user environments.
numpy v2 just released a few hours ago and is already causing problems elsewhere 🫠 , need to wait for other packages (such as skimage) to make new released compiled against numpy v2