uncertainties

• fix support for Numpy 2.0 (#245). Note: uncertainties.unumpy still provides umatrix based on numpy.matrix. With numpy.matrix discouraged, umatrix is too, and will be dropped in a future release.
• fix automated running and reporting of code coverage with tests (#246)
• use setuptools-scm for setting version number from git tag (#247)

Fixes for build, deployment, and docs

• Use explicit package list to make sure unumpy is included (#232)
• Use setuptools-scm to make sure all files are in the source distribution (#235)
• updates to configuration for and links to readthedocs documentation. (#239)
• use double backticks more uniformly in docs. (#240)
• fixes to README.rst to allow it to render (needed for PyPI upload) (#243)

3.2.0 2024-June-02

Version 3.2.0 is the first release of Uncertainties in nearly two years and the
first minor release in over five years. It marks the beginning of an effort to
refresh and update the project with a new and expanded team of maintainers.

• Main Changes

  • Moved code development to lmfit organization, with 4 maintainers.
  • Update documentation.
  • Drop future dependency. Uncertainties now has no external dependencies when
    not using Numpy integration (Drop official support for Python versions before 3.8 #200).
  • Drop support for Python versions before 3.8, including Python 2 (Drop official support for Python versions before 3.8 #200)
  • remove 1to2 and deprecations (remove 1to2 and depreciations #214)

• Developer related changes

  • Moved from setup.py to pyproject.toml (Transition from setup.py to pyproject.toml #199)
  • Move tests to tests folder (Move tests to tests folder #216)
  • Update unumpy test to be compatible with numpy 2
  • Mark docstrings with backslashes as raw strings in tests (Mark docstrings with backslashes as raw strings #226)

See https://github.com/lebigot/uncertainties/issues/145.

The pretty-print and LaTeX formats can now be customized: the symbols used can be changed (a centered dot can thus for instance be used instead of the usual multiplication symbol).

Unit tests were added for this.

More details are in the Sphinx documentation.

The new "p" formatting tag forces parentheses around the … ± … part of printed numbers.

There is now a single code base for Python 2 and Python 3.

Python 2.7 is now the minimal Python version.

The installation can also now be done through a universal wheel, which helps with some external projects (see issue https://github.com/lebigot/uncertainties/issues/106, for instance).

This Git version should have the same uncertainties code as PyPI version 3.1.4, but some accompanying files have been updated. This should have no impact on users. Developers are better off using this Git 3.1.4 version.

Starting with NumPy 1.17, numpy.linalg.pinv has a None __defaults__ attribute, for which the code made no provision. This is fixed.

correlated_values() now again accepts variables with a 0 variance. This was broken by version 3.1.

The deprecation warning raised by inspect.getargspec() in recent versions of Python 3 is now gone.

A calculation like str(sum(ufloat(1, 1) for _ in xrange(100000))) is now about 5,000 faster than with the latest release (version 2.4.8.1).

More generally, the calculation time of such sums (and more generally of complex expressions involving many numbers with uncertainty) is now linear instead of quadratic, and much faster in absolute time.

This closes issue https://github.com/lebigot/uncertainties/issues/30.

±inf±… can now be printed and formatted.

This is consistent with the fact that such numbers with uncertainty can be created with uncertainties.ufloat().

This makes it easier to handle calculation that work with floats despite involving infinities.

"python3 setup.py install" failed when setuptools was not installed. This is now fixed (by running 2to3 in setup.py when setuptools is not available, since distutils does not do it automatically).

The string and empty format type formatting of numbers with uncertainties are now similar to what Python 3.4 does (https://docs.python.org/3.4/library/string.html#format-specification-mini-language).

The previous behavior was based on the Python 2.7 documentation, which is probably incorrect (http://stackoverflow.com/questions/16525924/precise-definition-of-float-string-formatting).

Numbers like NaN±… can now be formatted.

An exception is now raised for negative standard deviations. This fixes a regression probably introduced by version 2.

Workaround for NumPy 1.8.0 new mean() behavior, which made uncertainties fail when calculating the mean of an array with numbers with uncertainties.

Reference: https://github.com/numpy/numpy/issues/4063

The uncertainties.umath functions ceil(), floor(), isinf(), isnan() and trunc() now return values of the same type as their corresponding function in the math module.

In previous versions, they generally returned values with a zero uncertainty (…±0), which was not useful, since the results of these functions are integers (float or int type) or booleans. It is less surprising to obtain the same types as in the math module.

This version adds extensive support for formatting, including automatic and user-defined control of the uncertainty format, and pretty-printing and LaTeX formatting.