AnyPyTools version 1.4.6

Update tests

AnyPyTools version 1.4.5

Fixed a small issue with using AnyPyTools with pytest 6.0.0rc1

AnyPyTools version 1.4.4

• Addressed a deprecation warning from pytest plugin due to API change in pytest 5.4
• Fix a syntax warning triggered in Python 3.8

AnyPyTools version 1.4.3

Fixed regression with Python 3.8 where model output could not be serialzed.

AnyPyTools version 1.4.2

Fixed:

• A potential bug when using the pytest plugin and expected errors in AnyScript test files.
• Fixed a bug with the pytest plugin not working with pytest 5.4

AnyPyTools version 1.4.1

• Fixed a bug where log files would be removed even if the processing failed.

AnyPyTools version 1.4

• Progressbars are now draw using tqdm <https://github.com/tqdm/tqdm>__. This enables error
  messages while the progress bar is rendering, and solves a problem with detecting when the
  code is running in Jupyter notebook and not.
• Running the pytest plugin with the --anytest-save argument now deselects
  all tests which doesn't save data to HDF 5 files.
• New option for running the GUI version of AMS with AnyPyTools instead of the console.
• Task meta info (i.e. task_logfile, task_macro etc.) are now hidden by default in the
  when printing the object witht the default __repr__()
• The return_task_info argument to AnyPyProcess class is now deprecated and task information is
  always include in the output.

AnyPyTools version 1.3.0

Changed:

• Changed the interface for the pytest plugin when saving hdf5 files from anybody tests.

AnyPyTools version 1.2.2

• Fixed problem with Ctrl-C events not working. scipy.stats used
  some fortran routines which hijacked the key event and caused a crash instead.

• Fixed an issue with process time not being reported correctly.

• Fixed an issue with macros which were a mixture of normal strings and macro-command helper
  classes from anypytools.macro_commands.

AnyPyTools version 1.2.1

Fixed:

• Add a work-around for a bug in AnyBody <= 7.2.1 which cause the AnyBody console
  to start in interactive mode when launched from AnyPyTools. This could cause the
  console application to hang if something fails in AnyBody.