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
On further investigation, looks like the NumPy issue was an issue resolved in main. So a release will fix that problem (more reason to get a release out)
In terms of Python 3.12, things largely worked, but had to fix an entrypoint test issue: #471
Side note: Think it is time for us to drop Python 3.8. Have raised as issue ( zarr-developers/community#65 ). If we would rather have a release with Python 3.8 first, then drop Python 3.8 right after, that is fine. That is, as long as CI remains cooperative (there were some issues cropping up recently with Python 3.8 builds in the Python 3.12 PR). Though would also be ok just dropping it in the Python 3.12 PR (as part of this release)
Seeing some sporadic issues with macOS CI where it tries to use AVX2 instructions. We might want to just turn this off completely. Doubt CI has hardware to cover this instruction. Though unsure why this issue is coming up now
Activity
martindurant commentedon May 26, 2023
I support a release
joshmoore commentedon May 31, 2023
Shall we roll out 0.12.0 and 2.15.0 together, @jakirkham?
jsolbrig commentedon Sep 21, 2023
Will 0.12.0 be released sometime soon? I'm really anticipating #428 being released.
jakirkham commentedon Oct 3, 2023
There was a bug encountered with NumPy 1.26+, which would be good to fix: #470
Given Python 3.12 is out, we might want to add that to CI (wouldn't expect other changes needed)
IDK if we want to wait to release for these things or release and then re-release whenever those fixes land
joshmoore commentedon Oct 4, 2023
I'd tend to get a release out ASAP (or ASAJIH -- "as soon as John is happy") and then roll another.
jakirkham commentedon Oct 4, 2023
On further investigation, looks like the NumPy issue was an issue resolved in
main. So a release will fix that problem (more reason to get a release out)In terms of Python 3.12, things largely worked, but had to fix an entrypoint test issue: #471
Side note: Think it is time for us to drop Python 3.8. Have raised as issue ( zarr-developers/community#65 ). If we would rather have a release with Python 3.8 first, then drop Python 3.8 right after, that is fine. That is, as long as CI remains cooperative (there were some issues cropping up recently with Python 3.8 builds in the Python 3.12 PR). Though would also be ok just dropping it in the Python 3.12 PR (as part of this release)
jakirkham commentedon Oct 6, 2023
Went ahead and merged PR: #471
Going to kick off the release
jakirkham commentedon Oct 6, 2023
Have tagged the release here: https://github.com/zarr-developers/numcodecs/releases/tag/v0.12.0
jakirkham commentedon Oct 6, 2023
Seeing some sporadic issues with macOS CI where it tries to use AVX2 instructions. We might want to just turn this off completely. Doubt CI has hardware to cover this instruction. Though unsure why this issue is coming up now
Tracking in issue: #473
jakirkham commentedon Oct 6, 2023
Now available on PyPI & conda-forge! 🚀
Closing...
jakirkham commentedon Oct 18, 2023
As noted elsewhere, there were a couple bugs that surfaced recently. Most notably issue ( #478 ). Fixes for these are now in
Have cut 0.12.1. Wheels are already up. Conda-forge packages are in progress: conda-forge/numcodecs-feedstock#101
rabernat commentedon Oct 18, 2023
Thanks for your work @jakirkham! Appreciate it! 🙏
jakirkham commentedon Oct 18, 2023
Packages are up on conda-forge. Just waiting for them to mirror to CDN. Typically that takes ~15mins after upload (though could be longer)