• Files Changed
• Browse Source

- update to 2.9.0:
  * Support for PyPy (see PRs #467 and #740).  The full test suite
    should pass now, at least for the 3.10 version.
    providing help and additional fixes.
  * Fixed more sanitizer issues (see PR #469).
  * Modernized the test suite to avoid some warnings.

• Files Changed
• Browse Source

- update to 2.8.8:
  * Fix re_evaluate not taking global_dict as argument.
  * Fix parsing of simple complex numbers.  Now,
    `ne.evaluate('1.5j')` works.
  * Fixes for upcoming NumPy 2.0

• Files Changed
• Browse Source

- update to 2.8.7:
  * More permissive rules in sanitizing regular expression: allow to
    access digits after the . with scientific notation.
  * Don't reject double underscores that are not at the start or end of
    a variable name (pandas uses those), or scientific-notation numbers
    with digits after the decimal point.
  * Do not use numpy.alltrue in the test suite, as it has been
    deprecated (replaced by numpy.all).
  * Python 3.12 support

  * Thanks to Kirill Kouzoubov for a range of fixes to constants parsing that was
  * Thanks to Mark Harfouche for noticing that we no longer need `numpy` version
- skip python3.6 build (no numpy)
- python3 package added
 * Fixed several issues with different platforms not supporting
 * Now, when trying to use pure Python boolean operators, 'and',
 'or' and 'not, an error is issued and suggesting that '&', '|'
- fix requiements for SLE 11

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- update to 2.8.4:
  * Support for Python 3.11 has been added.
  * Thanks to Tobias Hangleiter for an improved accuracy complex `expm1` function.
    While it is 25 % slower, it is significantly more accurate for the real component
    over a range of values and matches NumPy outputs much more closely.
  * Thanks to Kirill Kouzoubov for a range of fixes to constants parsing that was 
    resulting in duplicated constants of the same value.
  * Thanks to Mark Harfouche for noticing that we no longer need `numpy` version 
    checks. `packaging` is no longer a requirement as a result.

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- skip python3.6 build (no numpy) 

- 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.

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- 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.

• Files Changed
• Browse Source

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

Update to 2.6.2
Implement single-spec version

• Files Changed
• Browse Source