Getting ready for release 2.7.2

Author: robbmcleod

.gitignore

@@ -3,6 +3,7 @@ syntax: glob
 build/
 build-cmake/
 dist/
+artifact/
 numexpr.egg-info/
 *.pyc
 *.swp

ANNOUNCE.rst

@@ -1,12 +1,16 @@
 ========================
-Announcing Numexpr 2.7.2
+Announcing NumExpr 2.7.2
 ========================
 
 Hi everyone, 
 
-This is a change in behavior for the Intel VML (Vector Math Library) version, in
-that it no longer forces the VML threads to 1, as this could have a negative 
-effect on the performance of NumPy itself when it is built with MKL.
+It's been awhile since the last update to NumExpr, mostly as the existing scientific 
+Python tool chain for building wheels on PyPi became defunct and we have had to 
+redevelop a new one based on `cibuildwheel` and GitHub Actions. This release also
+brings us support (and wheels for) Python 3.9.
+
+There have been a number of changes to enhance how NumExpr works when NumPy 
+uses MKL as a backend.
 
 Project documentation is available at:
 
@@ -15,6 +19,10 @@ http://numexpr.readthedocs.io/
 Changes from 2.7.1 to 2.7.2
 ---------------------------
 
+- Support for Python 2.7 and 3.5 is deprecated and will be discontinued when 
+  `cibuildwheels` and/or GitHub Actions no longer support these versions.
+- Wheels are now provided for Python 3.7, 3.5, 3.6, 3.7, 3.8, and 3.9 via 
+  GitHub Actions.
 - The block size is now exported into the namespace as `numexpr.__BLOCK_SIZE1__`
   as a read-only value.
 - If using MKL, the number of threads for VML is no longer forced to 1 on loading 
@@ -24,6 +32,10 @@ Changes from 2.7.1 to 2.7.2
 - Use of `ndarray.tostring()` in tests has been switch to `ndarray.tobytes()` 
   for future-proofing deprecation of `.tostring()`, if the version of NumPy is 
   greater than 1.9.
+- Added a utility method `get_num_threads` that returns the (maximum) number of 
+  threads currently in use by the virtual machine. The functionality of 
+  `set_num_threads` whereby it returns the previous value has been deprecated 
+  and will be removed in 2.8.X.
 
 What's Numexpr?
 ---------------

README.rst

@@ -2,28 +2,28 @@
 NumExpr: Fast numerical expression evaluator for NumPy
 ======================================================
 
-:Author: David M. Cooke, Francesc Alted and others
-:Contact: [email protected]
+:Author: David M. Cooke, Francesc Alted, and others.
+:Maintainer: Robert A. McLeod
+:Contact: [email protected]
 :URL: https://github.com/pydata/numexpr
 :Documentation: http://numexpr.readthedocs.io/en/latest/
 :Travis CI: |travis|
-:Appveyor: |appveyor|
+:GitHub Actions: |actions|
 :PyPi: |version|
 :DOI: |doi|
 :readthedocs: |docs|
 
+.. |actions| image:: https://github.com/pydata/numexpr/workflows/Build/badge.svg
+        :target: https://github.com/pydata/numexpr/actions
 .. |travis| image:: https://travis-ci.org/pydata/numexpr.png?branch=master
         :target: https://travis-ci.org/pydata/numexpr
-.. |appveyor| image:: https://ci.appveyor.com/api/projects/status/we2ff01vqlmlb9ip
-        :target: https://ci.appveyor.com/project/robbmcleod/numexpr
 .. |docs| image:: https://readthedocs.org/projects/numexpr/badge/?version=latest
         :target: http://numexpr.readthedocs.io/en/latest
 .. |doi| image:: https://zenodo.org/badge/doi/10.5281/zenodo.2483274.svg
         :target:  https://doi.org/10.5281/zenodo.2483274
 .. |version| image:: https://img.shields.io/pypi/v/numexpr.png
         :target: https://pypi.python.org/pypi/numexpr
 
-
 What is NumExpr?
 ----------------
 

RELEASE_NOTES.rst

@@ -5,6 +5,10 @@ Release notes for Numexpr 2.7 series
 Changes from 2.7.1 to 2.7.2
 ---------------------------
 
+- Support for Python 2.7 and 3.5 is deprecated and will be discontinued when 
+  `cibuildwheels` and/or GitHub Actions no longer support these versions.
+- Wheels are now provided for Python 3.7, 3.5, 3.6, 3.7, 3.8, and 3.9 via 
+  GitHub Actions.
 - The block size is now exported into the namespace as `numexpr.__BLOCK_SIZE1__`
   as a read-only value.
 - If using MKL, the number of threads for VML is no longer forced to 1 on loading 

RELEASING.md

@@ -1,121 +1,95 @@
+Releasing NumExpr
 ==================
-Releasing Numexpr
-==================
-
-:Author: Francesc Alted
-:Contact: [email protected]
-:Date: 2009-06-02
 
+* Author: Robert A. McLeod
+* Contact: [email protected]
+* Date: 2020-12-28
 
-Following are notes useful for releasing Numexpr.
+Following are notes for releasing NumExpr.
 
 Preliminaries
 -------------
 
-- Make sure that ``RELEASE_NOTES.txt`` and ``ANNOUNCE.txt`` are up to
-  date with the latest news in the release.
+* Make sure that `RELEASE_NOTES.rst` and `ANNOUNCE.rst` are up to date with the latest news in the release.
+* Remove the `.devN` suffix in `numexpr/version.py`.
+* Do a commit and a push:
 
-- Remove the `.devN` suffix in ``numexpr/version.py``.
+    `git commit -a -m "Getting ready for release X.Y.Z"`
 
-- Do a commit and a push:
+* If the directories `dist` or `artifact` exist delete them.
 
-  $ git commit -a -m"Getting ready for release X.Y.Z"
-
-Testing
--------
-
-- Run the test suite in different platforms (at least Linux and
-  Windows) and make sure that all tests passes.
-
-- Re-compile with MKL support and see if all tests passes as well.
+Local Testing
+-------------
 
-- Run all the benchmarks in ``bench/`` directory and see if the
+* Re-compile locally with MKL support and see if all tests passes as well.
+* Run all the benchmarks in `bench/` directory and see if the
   speed-ups are the expected ones.
 
-Packaging
----------
-
-- Make the tarball with the command:
-
-  $ python setup.py sdist
-
-  Do a quick check that the tarball is sane.
-
-Releasing
----------
-
-- Create a tag ``vX.Y.Z`` from ``master``.  Use the next message:
+Tagging
+-------
 
-  $ git tag -a vX.Y.Z -m "Tagging version X.Y.Z"
+* Create a tag `vX.Y.Z` from `master` and push the tag to GitHub:
 
-- Push the tag to the github repo:
+    `git tag -a vX.Y.Z -m "Tagging version X.Y.Z"`
+    `git push`
+    `git push --tags`
 
-  $ git push
-  $ git push --tags
+* If you happen to have to delete the tag, such as artifacts demonstrates a fault, first delete it locally,
 
-- If you happen to have to delete the tag, for example if the `manywheels` builds 
-  demonstrates a fault, first delete it locally,
+    `git tag --delete vX.Y.Z`
 
-      git tag --delete vX.Y.Z
-  
   and then remotely on Github,
 
-      git push --delete origin vX.Y.Z
+    `git push --delete origin vX.Y.Z`
 
-Build wheels
+Build Wheels
 ------------
 
-Matthew Brett has a repository for building for hosting wheels at
-http://github.com/MacPython/numexpr-wheels). For the procedure to trigger and
-upload the built wheels, see the README at that repo.
+* Check on GitHub Actions `github.com/robbmcleod/cpufeature/actions` that all the wheels built successfully.
+* Download `artifacts.zip` and unzip.
+* Make the source tarball with the command
 
-Build and upload the wheels before uploading the source distribution, to make
-sure that people who do not have compilers do not get breakage while the
-release is being uploaded.
+    `python setup.py sdist`
+
+Releasing
+---------
 
-Any problems, feel free to ask @matthew-brett for help - or indeed, pass the
-whole task to him.
+* Upload the built wheels to PyPi via Twine.
 
-Uploading the source distribution
----------------------------------
+    `twine upload artifact/numexpr*.whl`
 
-- Upload it in the PyPi repository:
+* Upload the source distribution.
 
-  $ python setup.py sdist upload
+    `twine upload dist/numexpr-X.Y.Z.tar.gz`
+
+* Check on `pypi.org/project/numexpr/#files` that the wheels and source have uploaded as expected.
 
 
 Announcing
 ----------
 
-- Send an announcement to the NumPy list, PyData and python-announce
-  list.  Use the ``ANNOUNCE.rst`` file as skeleton (or possibly as the
-  definitive version).
-
+* Send an announcement to the NumPy list, PyData and python-announce
+  list.  Use the `ANNOUNCE.rst` file as skeleton (or possibly as the
+  definitive version). Email should be addressed to the following lists:
+  * [email protected]
+  * [email protected]
+  * [email protected]
 
 Post-release actions
 --------------------
 
-- Edit ``numexpr/version.py`` to bump the version revision
+* Edit `numexpr/version.py` to bump the version revision
   (i.e. X.Y.Z --> X.Y.(Z+1).dev0).
-
-- Create new headers for adding new features in ``RELEASE_NOTES.txt``
+* Create new headers for adding new features in `RELEASE_NOTES.rst`
   and add this place-holder:
 
-  #XXX version-specific blurb XXX#
+  `* **Under development.**`
 
   Don't forget to update header to the next version in those files.
 
-- Commit your changes:
+* Commit your changes:
 
   $ git commit -a -m"Post X.Y.Z release actions done"
   $ git push
 
-
-That's all folks!
-
-
-.. Local Variables:
-.. mode: rst
-.. coding: utf-8
-.. fill-column: 70
-.. End:
+Fin.