blosc2 2.3.0__tar.gz → 2.3.1__tar.gz

{blosc2-2.3.0 → blosc2-2.3.1}/.github/workflows/cibuildwheels.yml

@@ -68,6 +68,8 @@ jobs:
       - name: Build wheels
         run: |
           python -m cibuildwheel --output-dir wheelhouse
+        env:
+          CIBW_CONFIG_SETTINGS: "--build-option=-DDEACTIVATE_AVX512:BOOL=YES"
 
       - name: Upload wheels
         uses: actions/upload-artifact@v3
@@ -116,7 +118,7 @@ jobs:
           cd ./dist
           tar -xzf blosc2-*.tar.gz
           cd ./blosc2-*/
-          python setup.py build_ext --inplace
+          python setup.py build_ext --inplace -DDEACTIVATE_AVX512:BOOL=YES
 
       - name: Test sdist package with pytest
         run: |

{blosc2-2.3.0 → blosc2-2.3.1}/ANNOUNCE.rst

@@ -1,12 +1,13 @@
-Announcing Python-Blosc2 2.3.0
+Announcing Python-Blosc2 2.3.1
 ==============================
 
-This new minor release adds methods to handle NDArrays serialized into memory
-frames, and allows opening super-chunks stored in container files (like HDF5)
-by their offset.  C-Blosc2 is updated to the latest stable version, which
-provides support for AVX512 and fixes compatibility with ARM platforms
-(e.g. Raspberry Pi).  Cython 3 is now required for building, and other minor
-fixes and additions are included as well.
+The new minor release 2.3 adds methods to handle NDArrays serialized into
+memory frames, and allows opening super-chunks stored in container files (like
+HDF5) by their offset.  C-Blosc2 is updated to the latest stable version,
+which provides support for AVX512 (temporarily disabled in wheels) and fixes
+compatibility with ARM platforms (e.g. Raspberry Pi).  Cython 3 is now
+required for building, and other minor fixes and additions are included as
+well.
 
 For more info, you can have a look at the release notes in:
 

{blosc2-2.3.0/blosc2.egg-info → blosc2-2.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: blosc2
-Version: 2.3.0
+Version: 2.3.1
 Summary: Python wrapper for the C-Blosc2 library
 Author-email: Blosc Development Team <blosc@blosc.org>
 Maintainer-email: Blosc Development Team <blosc@blosc.org>

{blosc2-2.3.0 → blosc2-2.3.1}/RELEASE_NOTES.md

@@ -1,5 +1,10 @@
 # Release notes
 
+## Changes from 2.3.0 to 2.3.1
+
+* Temporarily disable AVX512 support in C-Blosc2 for wheels built by CI until
+  run-time detection works properly.
+
 ## Changes from 2.2.9 to 2.3.0
 
 * Require at least Cython 3 for building. Using previous versions worked but

{blosc2-2.3.0 → blosc2-2.3.1}/RELEASING.rst

@@ -4,10 +4,10 @@ python-blosc2 release procedure
 Preliminaries
 -------------
 
-* Check that `VERSION` file contains the correct number.
+* Check that ``VERSION`` file contains the correct number.
 
 * Make sure that the c-blosc2 submodule is updated to the latest version (or a specific
-  version that will be documented in the `RELEASE_NOTES.md`)::
+  version that will be documented in the ``RELEASE_NOTES.md``)::
 
     cd blosc2/c-blosc2
     git pull
@@ -24,7 +24,7 @@ Preliminaries
 
 is printing the correct versions.
 
-* Make sure that `RELEASE_NOTES.md` and `ANNOUNCE.rst` are up to date with the latest news
+* Make sure that ``RELEASE_NOTES.md`` and ``ANNOUNCE.rst`` are up to date with the latest news
   in the release.
 
 * Commit the changes::
@@ -33,12 +33,12 @@ is printing the correct versions.
     git push
 
 * Double check that the supported Python versions for the wheels are the correct ones
-  (`.github/workflows/cibuildwheels.yml`).  Add/remove Python version if needed.
-  Also, update the `classifiers` field for the supported Python versions.
+  (``.github/workflows/cibuildwheels.yml``).  Add/remove Python version if needed.
+  Also, update the ``classifiers`` field for the supported Python versions.
 
 * Check that the metainfo for the package is correct::
 
-    python -m build --sdist 
+    python -m build --sdist
     twine check dist/*
 
 
@@ -47,14 +47,19 @@ Tagging
 
 * Create a (signed, if possible) tag ``X.Y.Z`` from ``main``.  Use the next message::
 
-    git tag -a vX.Y.Z -m "Tagging version X.Y.Z"
+    git tag -a vX.Y.Z -m "Tagging python-blosc2 version X.Y.Z"
 
 * Push the tag to the github repo::
 
     git push --tags
 
-* Go to Blosc/blogsite repo and click on the `Re-run all jobs` button to regenerate the
-  documentation and check that it has been correctly updated in https://www.blosc.org.
+* Make sure that the tag is passing the tests in continuous integration (this
+  may take more than an hour).
+
+* Go to ``Blosc/blogsite`` repo, then to "Actions", click on the most recent
+  workflow run (at the top of the list), and then click on the "Re-run all
+  jobs" button to regenerate the documentation and check that it has been
+  correctly updated in https://www.blosc.org.
 
 
 Checking packaging
@@ -62,7 +67,8 @@ Checking packaging
 
 * Do an actual release in github by visiting:
   https://github.com/Blosc/python-blosc2/releases/new
-  Add the notes specific for this release.
+  Add the notes specific for this release
+  (you may want to remove newlines for aesthetics).
   This will upload the wheels to PyPI too.
 
 * Check that the package (and wheels!) have been uploaded to PyPI
@@ -72,8 +78,9 @@ Checking packaging
 * Check that the packages and wheels are sane::
 
     python -m pip install blosc2 -U
+    pip install -r requirements-test-wheels.txt
     cd tests
-    python -c"import blosc2; blosc2.print_versions()"
+    python -c "import blosc2; blosc2.print_versions()"
     pytest
 
 
@@ -93,13 +100,15 @@ Post-release actions
 
     cd $HOME/blosc/python-blosc2
 
-* Create new headers for adding new features in ``RELEASE_NOTES.md``
-  add this place-holder:
+* Create a new header for adding new features in ``RELEASE_NOTES.md``
+  with a placeholder text::
+
+    ## Changes from X.Y.Z to X.Y.(Z+1)
 
-  XXX version-specific blurb XXX
+    XXX version-specific blurb XXX
 
 * Edit ``VERSION`` in master to increment the version to the next
-  minor one (i.e. X.Y.Z --> X.Y.(Z+1).dev0).
+  patch one (i.e. X.Y.Z --> X.Y.(Z+1).dev0).
 
 * Commit your changes with::
 

blosc2-2.3.1/VERSION

@@ -0,0 +1 @@
+2.3.1

blosc2-2.3.1/blosc2/version.py

@@ -0,0 +1 @@
+__version__ = "2.3.1"

{blosc2-2.3.0 → blosc2-2.3.1/blosc2.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: blosc2
-Version: 2.3.0
+Version: 2.3.1
 Summary: Python wrapper for the C-Blosc2 library
 Author-email: Blosc Development Team <blosc@blosc.org>
 Maintainer-email: Blosc Development Team <blosc@blosc.org>

blosc2-2.3.0/VERSION

@@ -1 +0,0 @@
-2.3.0

blosc2-2.3.0/blosc2/version.py

@@ -1 +0,0 @@
-__version__ = "2.3.0"