forked from pool/python-numexpr
Accepting request 632752 from home:apersaud:branches:devel:languages:python:numeric
update to latest version OBS-URL: https://build.opensuse.org/request/show/632752 OBS-URL: https://build.opensuse.org/package/show/devel:languages:python:numeric/python-numexpr?expand=0&rev=5
This commit is contained in:
committed by
Git OBS Bridge
parent
298459f738
commit
d833fbec74
@@ -1,3 +1,26 @@
|
||||
-------------------------------------------------------------------
|
||||
Sun Sep 2 16:48:00 UTC 2018 - arun@gmx.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.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 6 20:04:09 UTC 2018 - toddrme2178@gmail.com
|
||||
|
||||
|
||||
Reference in New Issue
Block a user