Skip to content

Release 1.2.1

Compare
Choose a tag to compare
@florianschanda florianschanda released this 22 Sep 07:31

1.2.1

  • New minor version release due to minor API changes and major command-line changes.

  • When using --verify you can now also specify a CVC5 executable using --use-cvc5-binary. This allows you to use the --verify option on platforms where there is no CVC5 PyPI package (i.e. Windows or more recent versions of OSX).

  • The PyVCG package is now required on all platforms. The optional dependency is now CVC5 instead.

  • Remove the --lint option. Lint messages are now enabled by default, and .trlc files are processed as well. Instead there is a --no-lint option which turns off the extra warnings.

  • Add the --skip-trlc-files option which disables processing of .trlc files. Enabling this option is equivalent to the old --lint mode.

  • Add the --error-on-warnings option which generates a status code of 1 if any warning is raised.

  • We now always print a short summary, indicating how many files were processed and how many messages were generated. The
    --show-file-list option still exists and still prints the complete list of files. This summary may be suppressed with the --brief option.

  • The Source_Manager has new and different constructor flags, although it can still be constructed with no parameters.

  • The Message_Handler now uses an enumeration instead of a string to signal message severity/kind. For normal use this is transparent, but if you subclass the message handler then you need to deal with this. The category (for lint messages) is now also a separate parameter instead of being baked into the message.

  • Please note that if you parse messages in CI, the regex has changed slightly.

  • Fix an issue where --skip-trlc-files would incorrectly register and parse the preamble of .trlc files.

  • Fix a spurious space in the summary output.

  • Fix support for Python 3.11. The package can now be installed without issues.

  • Fix issue in VCG where the matches function could be generated more than once. This was only an issue in the debug output and was not visible to users.