Pypyr

Latest version: v5.9.1

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

Scan your dependencies

Page 8 of 14

1.2.1

- regression problem with pypyr.steps.pype from previous release fixed
- no functional change

1.2.0

- improve API call-ability of pypyr by splitting the pipeline loading from running, allowing consumer to manage pipeline cache themselves. With great thanks for the excellent idea and implementation by Reskov!
- no functional change introduced with this version

1.1.1

- no functional change, only devops deployment update
- supersedes the v1.1.0 release. note that v1.1.0 is not on pypi because of a deployment issue that 1.1.1 rectifies.

1.1.0

- cli option to log to a file path in addition to the console using `--logpath`. With great thanks to rickardcronholm!
- slight BREAKING CHANGE for `--loglevel`: The previous shortening to `pypyr mypipe --log 10` won't work anymore. Use `pypyr mypipe --logl 10` if you don't want to type out `--loglevel`
- python 3.7 compatibility
- README help with shell examples

1.0.0

- _while_ loop decorator
- README help with examples for all decorators

0.11.0

- *foreach* decorator
- big refactor of stepsrunner. the new module `pypyr.dsl` contains classes (for now, `Step`), that model the pypyr pipeline yaml Domain Specific Language. this made foreach easier.
- some cleanup on consistent error types - KeyNotInContextError rather than KeyError for all context key lookup errors.
- big refactor of format strings aka string interpolation.
- optimize: no more unnecessary dict unpacking and repacking by now using `format_map(context)` rather than `format(**context)`
- single format expression now functions akin to a dictionary path in xpath style. e.g a string formatting expression like `'{key1[0]}'` will fetch the first item in the list at `key` and keep the original type of that item *without converting it to string*. In this example, the format expression would return a list:

key1:
- ['list', 'here']
- 1

- format expressions like `{key1} literal text {key2}` will obviously still return type strings

Page 8 of 14

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.