Parsita

Latest version: v2.1.1

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

Scan your dependencies

Page 2 of 4

1.6.1

Not secure
Maintenance release with no change in behavior:
* Add support for Python 3.10

1.6.0

Not secure
One new feature and a refactoring of the tests:
* Added the `TransformationParser` which is exposed through the `>=` operator
* All tests were refactored from unittest style to pytest style

1.5.0

Not secure
One new feature and a deprecation:

* Added the `LongestAlternativeParser` parser and its alias `longest` (21)
* Added `first` as an alias for `AlternativeParser`, which is the parser behind the `|` operator
* **Deprecation warning:** In Parsita 2.0, the `|` operator will use `longest` instead of `first`, and `AlternativeParser` will be renamed to `FirstAlternativeParser`. This is intended to make alternatives more intuitive. `first` and `longest` behave the same in most cases, but users should explicitly switch from `|` to `first` if the current behavior is desired.

A handful of other changes:
* Dropped Python 3.6 support
* Improved documentation and type hints of `Result`

Overhaul of infrastructure and some refactorings to latest Python features (no changes to package behavior):
* Created a [documentation website](https://parsita.drhagen.com/)
* Moved continuous integration from TravisCI to GitHub Actions
* Migrated the build system from setuptools to poetry
* Switched from tox to nox-poetry
* Added black and isort as code quality tools
* Refactored all string type annotations to use `from __future__ import annotations` now that Python 3.6 is gone
* Refactored all `.format` calls to use f-strings now that Python 3.5 is gone

1.4.1

Not secure
Maintenance release with no change in behavior:

* Add support for Python 3.9
* Drop support for Python 3.5
* Fix typos in README examples

1.4.0

Not secure
One new feature and a few minor bug fixes:

* Add the `PredicateParser`, which allows for a boolean-returning function to be applied to the result of a parser to determine if the result is acceptable
* Do not crash if `StringReader.next_token_regex` does not match
* In `RegexParser.__repr__`, appropriately prepend `name_or_nothing`
* Various fixes to type hints

Thanks to arseniiv for contributing to this release.

1.3.3

Not secure
Update supported Python versions:

* Add support for Python 3.8
* Drop support for Python 3.4
* Disallow instantiation of `Parsers` classes. This was never supposed to be allowed and now raises a good exception.

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.