If you can’t find a ready-made step that quite scratches your particular itch, don’t hesitate to code your own step - it’s easy, and very much the philosophy of pypyr that if you can write a quick couple of lines of python rather than contort your pipeline with clumsy step sequences, then do so! I know some frameworks don’t really encourage you to stray outside the prescribed features, but not so pypyr - your custom steps are first-class citizens of the pypyrverse.
You can freely mix your own custom steps and built-in steps in the same pipeline.
If you do code your own and you think it could be useful to the rest of the community, even if it’s trivial, check out the contribution guide for how to submit your code and then you can bask in the glow of making open-source a better place.
If you don’t code or that sounds like too much work, but you have an idea for a new step that would make your life better, feel very free to get in touch with a feature request.
import logging # getLogger will grab the parent logger context, so your loglevel and # formatting automatically will inherit correctly from the pypyr core. logger = logging.getLogger(__name__) def run_step(context): """Put your code in here. This shows you how to code a custom pipeline step. Args: context: dict-like. This is the entire pypyr context. You can mutate context in this step to make keys/values & data available to subsequent pipeline steps. Returns: None. """ logger.debug("started") # you probably want to do some asserts here to check that the input context # dictionary contains the keys and values you need for your code to work. context.assert_key_has_value(key='mykey', caller=__name__) # do this if you want your step to support substitutions. # get_formatted will also iterate mykey if it's an iterable # and do substitutions for each item in it. mystep_context = context.get_formatted('mykey') # assuming input context # mykey: # subkey: subkey value nested_value = mystep_context['subkey'] # get a context item if you don't care about substitutions context_item = context['arbkey'] # it's good form only to use .info and higher log levels when you must. # For .debug() being verbose is very much encouraged. logger.info("Your clever code goes here. . . ") # Add or edit context items. These are available to any pipeline steps # following this one. context['existingkey'] = 'new value overwrites old value' context['mynewcleverkey'] = 'new value' logger.debug("done")
The usual python import module resolution rules apply. pypyr will resolve
modules from the
first, which you can change by using the
Assuming you saved your python with the
def run_step(context) function in a
file like this
./dir/mystep.py, you can use use it in your pipeline like
steps: - step1 # runs ./step1.py - dir.mystep # runs ./dir/mystep.py
If you package your parser and you install the package into the active python environment, you can of course use the usual python absolute package name instead:
steps: - step1 - mypackage.mystep
All of the usual step decorators are available to your custom step. This makes it easy to use retry, looping and conditional logic on your custom step code without having to write any additional code.
steps: - step1 - name: mystep comment: run ./mystep.py pass input context values to the step. run step 3 times in total for "first", "second", "third" retry twice if the step fails. foreach: [first, second, third] in: set: your own context: input here so: your step can use it retry: max: 2 - step3