Comb-spec-searcher

Latest version: v4.2.0

Safety actively analyzes 630130 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

2.2.1

Fixed
- when passed a multivariate function, the `taylor_expand` function expands in
`x`.
- A division by zero error that occurred making the status update before
starting to run.

2.2.0

Added
- using Github Actions for testing and deployment
- add specification sharing function to `ForestSpecificationDrawer`

Changed
- when using a `LimitedStrategyRuleDB`, searching is aborted much faster when the root
is not in the first pruned rules dictionary

Fixed
- use `AbstractRule` instead of `Rule` in `_rules_from_strategy`
- fix `CombinatorialSpecification.share()` which was missing

2.1.1

Fixed
- fixed the type hints

2.1.0

Added
- a `SpecificationDrawer` for visualizing `CombinatorialSpecification`
- `show` method to `CombinatorialSpecification`
- `to_html_representation` method to `CombinatorialClass`
- `AbstractStrategy` raises `StrategyDoesNotApply` in the `__call__` method
- function `CombinatorialSpecification.share_spec()` which uploads the spec to a file
sharing site
- more verbose logging during the specification creation process

Changed
- Improved the status update
- `rule_from_equivalence_rule_dict` now takes a list of expected equivalence rules so a
much smaller dictionary is produced

Fixed
- fixed `ProofTree` handling of getting rules from spec
- fixed printing of `InvalidOperationError` message

2.0.0

Added
- the methods `expand_verified` and `expand_comb_class` on
`CombinatorialSpecification`
- the `get_rule` method on `CombinatorialSpecification` can also take a label
as a key
- `expand_verified` flag to the initialiser of
`CombinatorialSpecificationSearcher` which will expand verified classes using
the pack passed to the `CombinatorialSpecificationSearcher`
- `rule_from_equivalence_rule_dict` to `RuleDBBase`
- It is now possible to get all the combinatorial classes contained in a specification
with the `comb_classes` method.

Changed
- When expanding verified nodes in a specification, the search now uses
`_auto_search_rules`, instead of `do_level` and `get_smallest_specification`.
This is a stripped back auto search method returning the equivalence paths
and strategies needed to create a specification.
- the `get_eq_symbol` and `get_op_symbol` are moved to `AbstractStrategy`
rather than `Constructor`
- the `expand_verified` flag on the `auto_search` method and
`CombinitorialSpecification.__init__` method was removed, and the
default is now to not expand verified classes. You should use the
`expand_verified` method on `CombinatorialSpecification` for the same
behaviour.
It also no longer logs the string of the specification.

Fixed
- fixed sanity checking in `comb_spec_searcher`
- the initialiser of `CombinatorialSpecification` removes redundant rules

Removed
- `DisableLogging` was removed from `utils` as it is no longer used.

1.3.0

Added
- added an optional `fixed_values` parameter to the `DisjointUnion` constructor,
that allows you to set a value that a child's parameter must take.
- add the abstract method `can_be_equivalent` to `AbstractStrategy`.

Changed
- removed the method `is_equivalence` from `Constructor`. You should instead
use the `is_equivalence` method on the `Rule`.
- the `CartesianProduct` now considers compositions of all parameters and
not just `n`.
- the `RelianceProfile` type changed to work multiple parameters. It is now a
dictionary pointing from parameters to the values.

Fixed
- ignore rules where the left and non-empty right hand sides are the same

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.