v4.4.1

Author: nikohansen

README.md

@@ -89,6 +89,12 @@ It may be necessary to replace ``pip`` with ``python -m pip`` and/or prefixing
 either of these with ``sudo``.
 
 ## Version History
+* [Release ``4.4.1``](https://github.com/CMA-ES/pycma/releases/tag/r4.4.1)
+  - `fmin2` accepts a constraints function as `constraints` keyword argument
+  - an improved `CMAEvolutionStrategyResult2` class which also contains the best feasible solution
+  - a `reset_options` method which also clears the current termination status
+  - polish the output of ``.optimize()`` and of ``.result_pretty()``
+  - catch final ``.stop()`` value displayed with `cma.plot`
 
 * [Release ``4.4.0``](https://github.com/CMA-ES/pycma/releases/tag/r4.4.0)
   - constraints handling is available also in the <tt>ask</tt>-and-<tt>tell</tt> interface (addressing issues [#258](https://github.com/CMA-ES/pycma/issues/258), [#287](https://github.com/CMA-ES/pycma/issues/287), and [#167](https://github.com/CMA-ES/pycma/issues/167))

cma/__init__.py

@@ -103,7 +103,7 @@
 
 ___author__ = "Nikolaus Hansen and Petr Baudis and Youhei Akimoto"
 __license__ = "BSD 3-clause"
-__version__ = "4.4.0"
+__version__ = "4.4.1"
 
 
 import collections as _collections

setup-howto.py

@@ -7,8 +7,8 @@
 0.
 Run local tests
 
-    ./script-test-all-all-arm.sh
     ruff check cma
+    ./script-test-all-all-arm.sh
 
 1.
 Push to a test branch to trigger test:
@@ -67,10 +67,10 @@
 6.
 Loop over tests and distribution and fix code until everything is fine.
 
-7.
+7.a
 Draft a release on GitHub: click on releases and then new draft. Use above text added in README.md.
 
-8.a
+7.b
 Upload the distribution in ``install-folder``::
 
     twine upload dist/*  # upload everything given the install folder was clean
@@ -87,21 +87,21 @@
         twine upload --repository testpypi dist/cmae*
         cd ../install-folder
 
-8.b
+7.c
 EITHER: tag locally and push, mainly to avoid changing any remote branch::
 
     git tag -a r4.4.1 -m 'r4.4.1 release'
     git push origin r4.4.1
 
-OR: push code to development and/or master. This must be done at some
-    point anyways, if only to update the README.md, and::
+OR: push code to development and/or main. This must be done at some
+    point anyways, if only to update the README.md. Then, after 9. is done::
 
     git fetch  # or with --tags to fetch tags not followed remotely
 
-9.
+8.
 Finalize and publish the release drafted on Github.
 
-10.
+9.
 Push new docs to github
 
     cp -r apidocs/* /Users/hansen/git/CMA-ES.github.io/apidocs-pycma
@@ -110,8 +110,8 @@
     git ci
     git push
 
-11. (if not already done)
-Update master and push master and development to remote
+10. (if not already done)
+Update main and push main and development to remote
 
 
 Anaconda::

tools/conda.recipe/meta.yaml

@@ -1,5 +1,5 @@
 package:
-  version: "4.4.0"
+  version: "4.4.1"
   name: 'cma'
 
 source: