File python3-numexpr.changes of Package python3-numexpr
-------------------------------------------------------------------
Sun Sep 27 01:01:19 UTC 2015 - arun@gmx.de
- update to version 2.4.4:
* Honor OMP_NUM_THREADS as a fallback in case NUMEXPR_NUM_THREADS is
not set. Fixes #161. (PR #175, Stefan Erb).
* Added support for AppVeyor (PR #178 Andrea Bedini)
* Fix to allow numexpr to be imported after eventlet.monkey_patch(),
as suggested in #118 (PR #180 Ben Moran).
* Fix harmless data race that triggers false positives in
ThreadSanitizer. (PR #179, Clement Courbet).
* Fixed some string tests on Python 3 (PR #182, Antonio Valentino).
-------------------------------------------------------------------
Sat May 2 18:13:50 UTC 2015 - arun@gmx.de
- update to version 2.4.3:
* Comparisons with empty strings work correctly now. Fixes #121 and
PyTables #184.
-------------------------------------------------------------------
Thu Apr 23 15:28:19 UTC 2015 - arun@gmx.de
- update to version 2.4.2:
* Improved setup.py so that pip can query the name and version
without actually doing the installation. Thanks to Joris
Borgdorff.
-------------------------------------------------------------------
Tue Apr 14 22:49:27 UTC 2015 - arun@gmx.de
- specfile:
* update url
- update to version 2.4.1:
* Added more configuration examples for compiling with MKL/VML
support. Thanks to Davide Del Vento.
* Symbol MKL_VML changed into MKL_DOMAIN_VML because the former is
deprecated in newer MKL. Thanks to Nick Papior Andersen.
* Better determination of methods in cpuinfo module. Thanks to Marc
Jofre.
* Improved NumPy version determination (handy for 1.10.0). Thanks to
Åsmund Hjulstad.
* Benchmarks run now with both Python 2 and Python 3. Thanks to
Zoran Plesivčak.
-------------------------------------------------------------------
Sun Jan 10 00:51:53 UTC 2015 - arun@gmx.de
- specfile:
* update copyright year
* remove ifs for opensuse version <=1220
-------------------------------------------------------------------
Thu May 8 10:51:51 UTC 2014 - toddrme2178@gmail.com
- Update to 2.4
* A new `contains()` function has been added for detecting substrings
in strings. Only plain strings (bytes) are supported for now. See
PR #135 and ticket #142. Thanks to Marcin Krol.
* New version of setup.py that allows better management of NumPy
dependency. See PR #133. Thanks to Aleks Bunin.
- update to 2.3.1
* Added support for shift-left (<<) and shift-right (>>) binary operators.
See PR #131. Thanks to fish2000!
* Removed the rpath flag for the GCC linker, because it is probably
not necessary and it chokes to clang.
- update to 2.3
* Site has been migrated to https://github.com/pydata/numexpr. All
new tickets and PR should be directed there.
* [ENH] A `conj()` function for computing the conjugate of complex
arrays has been added. Thanks to David Menéndez. See PR #125.
* [FIX] Fixed a DeprecationWarning derived of using oa_ndim == 0 and
op_axes == NULL when using NpyIter_AdvancedNew() and NumPy 1.8.
Thanks to Mark Wiebe for advise on how to fix this properly.
-------------------------------------------------------------------
Tue Oct 22 13:32:08 UTC 2013 - toddrme2178@gmail.com
- update to 2.2.2
* The `copy_args` argument of `NumExpr` function has been brought
back. This has been mainly necessary for compatibility with
PyTables < 3.0, which I decided to continue to support. Fixed #115.
* The `__nonzero__` method in `ExpressionNode` class has been
commented out. This is also for compatibility with PyTables < 3.0.
See #24 for details.
* Fixed the type of some parameters in the C extension so that s390
architecture compiles. Fixes #116. Thank to Antonio Valentino for
reporting and the patch.
- update to 2.2.1
* Fixes a secondary effect of "from numpy.testing import `*`", where
division is imported now too, so only then necessary functions from
there are imported now. Thanks to Christoph Gohlke for the patch.
- update to 2.2
* [LICENSE] Fixed a problem with the license of the
numexpr/win32/pthread.{c,h} files emulating pthreads on Windows
platforms. After persmission from the original authors is granted,
these files adopt the MIT license and can be redistributed without
problems. See issue #109 for details
(https://code.google.com/p/numexpr/issues/detail?id=110).
* [ENH] Improved the algorithm to decide the initial number of threads
to be used. This was necessary because by default, numexpr was
using a number of threads equal to the detected number of cores, and
this can be just too much for moder systems where this number can be
too high (and counterporductive for performance in many cases).
Now, the 'NUMEXPR_NUM_THREADS' environment variable is honored, and
in case this is not present, a maximum number of *8* threads are
setup initially. The new algorithm is fully described in the Users
Guide now in the note of 'General routines' section:
https://code.google.com/p/numexpr/wiki/UsersGuide#General_routines.
Closes #110.
* [ENH] numexpr.test() returns `TestResult` instead of None now.
Closes #111.
* [FIX] Modulus with zero with integers no longer crashes the
interpreter. It nows puts a zero in the result. Fixes #107.
* [API CLEAN] Removed `copy_args` argument of `evaluate`. This should
only be used by old versions of PyTables (< 3.0).
* [DOC] Documented the `optimization` and `truediv` flags of
`evaluate` in Users Guide
(https://code.google.com/p/numexpr/wiki/UsersGuide).
-------------------------------------------------------------------
Thu Aug 15 08:09:29 UTC 2013 - speilicke@suse.com
- Only Buildrequire python3-2to3 on 12.2
- Buildrequire python3 on 12.2, we need sha512 module
-------------------------------------------------------------------
Mon May 6 06:23:38 UTC 2013 - highwaystar.ru@gmail.com
- initial python3 package
- update to 2.1
* New compatibility with Python 3:
* switch from PyString to PyBytes API (requires Python >= 2.6).
* fixed incompatibilities regarding the int/long API
* use the Py_TYPE macro
* use the PyVarObject_HEAD_INIT macro instead of PyObject_HEAD_INIT
* Dropped compatibility with Python < 2.6.
* Fixed several issues with different platforms not supporting
multithreading or subprocess properly (see tickets #75 and #77).
* Now, when trying to use pure Python boolean operators, 'and',
'or' and 'not, an error is issued and suggesting that '&', '|'
and '~' should be used instead (fixes #24).
