Slipcover

Latest version: v1.0.15

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

Scan your dependencies

Page 3 of 6

1.0.3

This release:
- adds a "show_contexts" field to the JSON coverage output, improving compatibility with `coverage.py` and codecov;
- works around a rare issue reading source code when it contains non-ASCII characters;

Thank you, guillaumeLepape, for figuring out the Codecov issue and providing a fix.

1.0.2

This release:
- adds `--version` to the command flags, to display SlipCover's version and exit;
- adds scanning for files never executed in the directories passed with `--source`, so that these, too, are included in the output;
- adds a summary line to the text version of the coverage results;
- fixes bugs computing the destination of certain branches when they occur within a `try` (including `except`, `except*`, `try`-`else` and `finally`). This affects only the branch destination shown, not their existence, counting, or statistics.

1.0.1

This release:

- adds Python 3.12 support, based on the new PEP669 (sys.monitoring) API, rather than bytecode rewriting;
- under Python 3.12, limits support for branch coverage to source files with less than ~32k lines. This is to facilitate adopting PEP669;
- changes the version number to 1.0.1, as this project is now (far) beyond being experimental.

0.3.2

This release fixes a bug which apparently only affects Python 3.10 when using branch coverage.

0.3.1

This release:
- fixes a bug instrumenting for branch coverage. The bug was leading to crashes during de-instrumentation on PyPy;
- continues the work towards making Slipcover more useful for guiding fuzzing;

Many thanks to cfbolz for figuring this bug out, including an [MRE](https://en.wikipedia.org/wiki/Minimal_reproducible_example) for it!

0.3.0

This version makes no visible changes to Slipcover when used as a coverage analyzer.
It starts to improve Slipcover's `import` interface, making it easier to use for coverage-guided fuzzing.

Page 3 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.