Next | Query returned 42 messages, browsing 21 to 30 | Previous

History of commit frequency

CVS Commit History:


   2020-10-12 23:52:05 by Jason Bacon | Files touched by this commit (87)
Log message:
math/blas, math/lapack: Install interchangeable BLAS system

Install the new interchangeable BLAS system created by Thomas Orgis,
currently supporting Netlib BLAS/LAPACK, OpenBLAS, cblas, lapacke, and
Apple's Accelerate.framework.  This system allows the user to select any
BLAS implementation without modifying packages or using package options, by
setting PKGSRC_BLAS_TYPES in mk.conf. See mk/blas.buildlink3.mk for details.

This commit should not alter behavior of existing packages as the system
defaults to Netlib BLAS/LAPACK, which until now has been the only supported
implementation.

Details:

Add new mk/blas.buildlink3.mk for inclusion in dependent packages
Install compatible Netlib math/blas and math/lapack packages
Update math/blas and math/lapack MAINTAINER approved by adam@
OpenBLAS, cblas, and lapacke will follow in separate commits
Update direct dependents to use mk/blas.buildlink3.mk
Perform recursive revbump
   2020-04-28 15:21:34 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-numexpr: updated to 2.7.1

Changes from 2.7.0 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.
   2019-11-09 22:36:15 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
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.
   2018-12-22 10:38:20 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
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.
   2018-08-30 13:01:35 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
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
   2018-08-14 15:43:25 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
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.
   2018-07-19 10:57:48 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
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.
   2018-07-04 10:10:08 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
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.
   2017-09-18 19:03:45 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
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.
   2017-09-14 12:52:01 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
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.

Next | Query returned 42 messages, browsing 21 to 30 | Previous