Log message:
py-numexpr: updated to 2.7.0

Changes from 2.6.9 to 2.7.0
- The default number of 'safe' threads has been restored to the historical limit
  of 8, if the environment variable "NUMEXPR_MAX_THREADS" has not been set.
- Thanks to @eltoder who fixed a small memory leak.
- Support for Python 2.6 has been dropped, as it is no longer available via
  TravisCI.
- A typo in the test suite that had a less than rather than greater than symbol
  in the NumPy version check has been corrected thanks to dhomeier.
- The file `site.cfg` was being accidently included in the sdists on PyPi.
  It has now been excluded.

Log message:
py-numexpr: updated to 2.6.9

Changes from 2.6.8 to 2.6.9
- Thanks to Mike Toews for more robust handling of the thread-setting
  environment variables.
- With Appveyor updating to Python 3.7.1, wheels for Python 3.7 are now
  available in addition to those for other OSes.

Log message:
py-numexpr: updated to 2.6.8

Changes from 2.6.7 to 2.6.8
---------------------------
- Add check to make sure that f_locals is not actually f_globals when we
  do the f_locals clear to avoid the 310 memory leak issue.
- Compare NumPy versions using distutils.version.LooseVersion to avoid issue
  312 when working with NumPy development versions.
- As part of multibuild, wheels for Python 3.7 for Linux and MacOSX are now
  available on PyPI

Log message:
py-numexpr: updated to 2.6.7

Changes from 2.6.6 to 2.6.7
* Thanks to Lehman Garrison for finding and fixing a bug that exhibited memory \ 
leak-like behavior. The use in numexpr.evaluate of sys._getframe combined with \ 
.f_locals from that frame object results an extra refcount on objects in the \ 
frame that calls numexpr.evaluate, and not evaluate’s frame. So if the calling \ 
frame remains in scope for a long time (such as a procedural script where \ 
numexpr is called from the base frame) garbage collection would never occur.
* Imports for the numexpr.test submodule were made lazy in the numexpr module.

Log message:
py-numexpr: updated to 2.6.6

Changes from 2.6.5 to 2.6.6:
Fix to the thread barrier that occassionally suffered from spurious wakeups on \ 
MacOSX.

Log message:
py-numexpr: updated to 2.6.5

Changes from 2.6.4 to 2.6.5
- The maximum thread count can now be set at import-time by setting the
  environment variable 'NUMEXPR_MAX_THREADS'. The default number of
  max threads was lowered from 4096 (which was deemed excessive) to 64.
- A number of imports were removed (pkg_resources) or made lazy (cpuinfo) in
  order to speed load-times for downstream packages (such as pandas, sympy,
  and tables). Import time has dropped from about 330 ms to 90 ms. Thanks to
  Jason Sachs for pointing out the source of the slow-down.
- Thanks to Alvaro Lopez Ortega for updates to benchmarks to be compatible with
  Python 3.
- Travis and AppVeyor now fail if the test module fails or errors.
- Thanks to Mahdi Ben Jelloul for a patch that removed a bug where constants
  in where calls would raise a ValueError.
- Fixed a bug whereby all-constant power operations would lead to infinite
  recursion.

Log message:
py-numexpr: update to 2.6.4

Changes from 2.6.3 to 2.6.4
- Christoph Gohkle noticed a lack of coverage for the 2.6.3
  `floor` and `ceil` functions for MKL that caused seg-faults in
   test, so thanks to him for that.

Log message:
py-numexpr: update to 2.6.3

Changes from 2.6.2 to 2.6.3
- Documentation now available at readthedocs.io_.
- Support for floor() and ceil() functions added by Caleb P. Burns.
- NumPy requirement increased from 1.6 to 1.7 due to changes in iterator
  flags.
- Sphinx autodocs support added for documentation on readthedocs.org.
- Fixed a bug where complex constants would return an error, fixing
  problems with `sympy` when using NumExpr as a backend.
- Fix for 277 whereby arrays of shape (1,...) would be reduced as
  if they were full reduction. Behavoir now matches that of NumPy.
- String literals are automatically encoded into 'ascii' bytes for
  convience.

Log message:
Changes 2.6.2:
Updates to keep with API changes in newer NumPy versions
Removed several warnings
Fix bugs in function stringcontains()
Detection of the POWER processor
Fix pow result casting
Fix integers to negative integer powers
Detect numpy exceptions in expression evaluation
Better handling of RC versions

Log message:
Update to 2.6.1.

Prompted by beta.repology.org.

Changes from 2.6.0 to 2.6.1

     * Fixed a performance regression in some situations as consequence of
       increasing too much the BLOCK_SIZE1 constant. After more careful
       benchmarks (both in VML and non-VML modes), the value has been set
       again to 1024 (down from 8192). The benchmarks have been made with
       a relatively new processor (Intel Xeon E3-1245 v5 @ 3.50GHz), so
       they should work well for a good range of processors again.
     * Added NetBSD support to CPU detection. Thanks to Thomas Klausner.