paulin/bonobo
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'master' of github.com:python-bonobo/bonobo

Browse Source
This commit is contained in:
Romain Dorgueil
2018-01-08 08:13:04 +01:00
parent e93ea8a803 857d3f9db3
commit cc08c1656f
11 changed files with 47 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/tutorial/0.5/tut01.rst
View File

@ -174,8 +174,8 @@ strategy). Actual behavior of an execution will depend on the strategy chosen, b
cases.
④ Before actually executing the `transformations`, the `ExecutorStrategy` instance will wrap each component in an
`execution context`, whose responsibility is to hold the state of the transformation. It enables to keep the
`transformations` stateless, while allowing to add an external state if required. We'll expand on this later.
`execution context`, whose responsibility is to hold the state of the transformation. It enables you to keep the
`transformations` stateless, while allowing you to add an external state if required. We'll expand on this later.
Concepts and definitions
::::::::::::::::::::::::

2
docs/tutorial/0.5/tut03.rst
View File

@ -15,7 +15,7 @@ Class-based transformations and configurables
Bonobo is a bit dumb. If something is callable, it considers it can be used as a transformation, and it's up to the
user to provide callables that logically fits in a graph.
You can use plain python objects with a `__call__()` method, and it ill just work.
You can use plain python objects with a `__call__()` method, and it will just work.
As a lot of transformations needs common machinery, there is a few tools to quickly build transformations, most of
them requiring your class to subclass :class:`bonobo.config.Configurable`.