SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG

 
 
Changelog for python38-numexpr-2.8.3-qubes.3.2.x86_64.rpm :

* Sun Jul 17 2022 Ben Greiner - Fix requirements
* Sat Jul 09 2022 Arun Persaud - specfile:
* require python >= 3.7- update to version 2.8.3:
* Support for Python 3.6 has been dropped due to the need to substitute the flag NPY_ARRAY_WRITEBACKIFCOPY for NPY_ARRAY_UPDATEIFCOPY. This flag change was initiated in NumPy 1.14 and finalized in 1.23. The only changes were made to cases where an unaligned constant was passed in with a pre-allocated output variable: ``` x = np.empty(5, dtype=np.uint8)[1:].view(np.int32) ne.evaluate(\'3\', out=x) ``` We think the risk of issues is very low, but if you are using NumExpr as a expression evaluation tool you may want to write a test for this edge case.
* Thanks to Matt Einhorn (AATTmatham) for improvements to the GitHub Actions build process to add support for Apple Silicon and aarch64.
* Thanks to Biswapriyo Nath (AATTbiswa96) for a fix to allow mingw builds on Windows.
* There have been some changes made to not import platform.machine() on sparc but it is highly advised to upgrade to Python 3.9+ to avoid this issue with the Python core package platform.- changes from version 2.8.2:
* skipped due to an error in uploading to PyPi.
* Mon Feb 07 2022 Arun Persaud - specfile:
* update copyright year
* skip build for python2- update to version 2.8.1:
* Fixed dependency list.
* Added \"pyproject.toml\" and modernize the \"setup.py\" script. Thanks to Antonio Valentino for the PR.- changes from version 2.8.0:
* Wheels for Python 3.10 are now provided.
* Support for Python 2.7 and 3.5 has been discontinued.
* All residual support for Python 2.X syntax has been removed, and therefore the setup build no longer makes calls to the `2to3` script. The `setup.py` has been refactored to be more modern.
* The examples on how to link into Intel VML/MKL/oneAPI now use the dynamic library.
* Fri Mar 12 2021 Dirk Müller - skip python3.6 build (no numpy)
* Wed Mar 03 2021 Arun Persaud - update to version 2.7.3:
* Pinned Numpy versions to minimum supported version in an effort to alleviate issues seen in Windows machines not having the same MSVC runtime installed as was used to build the wheels.
* ARMv8 wheels are now available, thanks to odidev for the pull request.
* Sat Jan 09 2021 Arun Persaud - specfile:
* update copyright year- update to version 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 the module. Testing has shown that VML never runs in multi-threaded mode for the default BLOCKSIZE1 of 1024 elements, and forcing to 1 can have deleterious effects on NumPy functions when built with MKL. See issue #355 for details.
* 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.
* Wed Jan 08 2020 Todd R - Update to 2.7.1
* Python 3.8 support has been added.
* Python 3.4 support is discontinued.
* The tests are now compatible with NumPy 1.18.
* site.cfg.example was updated to use the libraries tag instead of mkl_libs, which is recommended for newer version of NumPy.- Drop upstream-included fix_test.patch
* Sat Aug 31 2019 Arun Persaud - specfile:
* update copyright year
* added fix to call python in tests: fix_test.patch- update to version 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 AATTeltoder 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.
* Sat Dec 22 2018 Todd R - Update 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.
* Sun Sep 02 2018 arunAATTgmx.de- update to version 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.- changes from version 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.
 
ICM