Closed bendichter closed 5 months ago
Looks like this is unblocked as of v1.0.4 (https://github.com/inscopix/py_isx/issues/48#issuecomment-2033057806)
Looks like the test cases just need to be updated now - also a CHANGELOG entry
This is finally working. Though I think dropping 3.8 should probably be a different PR
I'll defer to @pauladkisson for PR review but mostly looks good to me
Though I think dropping 3.8 should probably be a different PR
For the global drop of 3.8 I would agree, and then we can do it synchronously throughout the ecosystem across the next few weeks (I think we have a couple of months still)
However, you would still need various skips of isx
stuff for 3.8 (such as in the CI installation step too) for this PR so maybe too much bother here?
Could do the 3.8 drop in separate PR, give that PR precedence, then come back to this?
Happy to review, but will have to wait until 5/20
@h-mayorquin I added a method as you suggested. I also added a test to ensure that the dtype of the data indeed matches this dtype extacted from the metadata (this did not match in a previous version of the isx package)
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 79.57%. Comparing base (
7aa2a63
) to head (6f2f8d4
). Report is 21 commits behind head on main.:exclamation: Current head 6f2f8d4 differs from pull request most recent head a41d30c. Consider uploading reports for the commit a41d30c to get more accurate results
blocked by https://github.com/inscopix/py_isx/issues/48