summaryrefslogtreecommitdiff
path: root/taskflow/examples/reverting_linear.py
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Cleanup some of the example code & docs"Jenkins2014-08-161-11/+5
|\
| * Cleanup some of the example code & docsJoshua Harlow2014-07-111-11/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | This commit makes a set of small adjustments to examples. - Rework some of the comments to be more clear. - Add links to the original source tree file. - Rename some of the examples to make it clear the concept the example is intented to show. - Move some common example functionality to the example utility file. Change-Id: I858e0dbf72fe8cb40a05bfdbb0857720ffb71c7f
* | Enabled hacking checks H305 and H307Christian Berendt2014-07-171-1/+0
|/ | | | | | | * H305 imports not grouped correctly * H307 like imports should be grouped together Change-Id: If1dd9c89f65ede6959865a885777cb08c263eca0
* Remove extraneous vim configuration commentsyangxurong2014-02-141-2/+0
| | | | | | | | | Remove line containing comment - # vim: tabstop=4 shiftwidth=4 softtabstop=4 Change-Id: I7581cc88b8de433d5609ed06c6570b0b45c13573 Closes-Bug:#1229324
* Misc minor fixes to taskflow/examplesChangbin Liu2014-01-031-1/+1
| | | | Change-Id: Iecf7693239d93e5a43cf5470bcfcdec605410ce4
* Fix up python 3.3 incompatabilitiesJoshua Harlow2013-11-211-1/+1
| | | | | | | | | | | | Make the python 3.3 testing work by selectively disabling & including eventlet, switch to testtools and testrepository which has 2.6, 2.7, 3.2+ unified testing support so that we can correctly run our tests in all supported python versions. Closes-Bug: #1251660 Co-authored-by: Alexander Gorodnev <agorodnev@griddynamics.com> Change-Id: I23b6f04387cfd3bf6b5a044edffa446ca897ce3a
* Update intro/comments for reverting_linear exampleJoshua Harlow2013-10-161-4/+33
| | | | Change-Id: Ib06ad263287eed122bfdd61965a9f26c9ec533e6
* Fix print statements for python 2/3Joshua Harlow2013-10-101-1/+1
| | | | Change-Id: Ic05af4d5defe26b729bd7dda3f04b790509bb155
* Bump requirements to the latestJoshua Harlow2013-10-051-0/+18
| | | | | | | | | | | Match the requirements for taskflow with the openstack requirements (note the upstream requirements are missing 'futures' and 'networkx') and update the new hacking violations that were detected due to the hacking requirement version bump. Change-Id: I8d1326cf2a8b1ea062f5e9aacd0c4f8261c6531a
* Simpler API to load flows into enginesIvan A. Melnikov2013-10-031-12/+9
| | | | | | | | | | | | | | | | | | | | | Previously to run a flow client code had to put together the flow, an engine, logbook, flowdetail, and storage backend. This commit adds two helper functions, run() and load(), so that simplest usecase now looks like taskflow.engines.run(flow) Client code may also provide configuration for storage and engine if needed, but if not needed it just works with defaults. Engines are loaded via stevedore, as drivers in 'taskflow.engines' backend. Now three entry points are defined in that namespace: - 'default', for SingleThreadedActionEngine, used by default; - 'serial', as another synonym for SingleThreadedActionEngine; - 'parallel', for MultiThreadedActionEngine. Closes-bug: #1224726 Change-Id: I7f4cb5c8ff7f5f12831ddd0952c202d2fd8cd6ef
* Engine, task, linear_flow unificationJoshua Harlow2013-09-051-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | In order to move away from the existing flows having their own implementation of running, start moving the existing flows to be patterns that only structure tasks (and impose constraints about how the group of tasks can run) in useful ways. Let the concept of running those patterns be handled by an engine instead of being handled by the flow itself. This will allow for varying engines to be able to run flows in whichever way the engine chooses (as long as the constraints set up by the flow are observed). Currently threaded flow and graph flow are broken by this commit, since they have not been converted to being a structure of tasks + constraints. The existing engine has not yet been modified to run those structures either, work is underway to remediate this. Part of: blueprint patterns-and-engines Followup bugs that must be addressed: Bug: 1221448 Bug: 1221505 Change-Id: I3a8b96179f336d1defe269728ebae0caa3d832d7
* Converted some examples to use patterns/enginesAnastasia Karpinska2013-09-041-24/+28
| | | | Change-Id: If7154019f1cb5e723069ff35f6301fce048323b5
* Rename "revert_with" => "revert" and "execute_with" to "execute"Changbin Liu2013-08-301-2/+2
| | | | | | | "_with" is kind of obvious, and also less typing for users of this library Change-Id: I99f597dae5612cc44cc7f19ae144776f63d32bac
* Check examples when running testsIvan A. Melnikov2013-08-271-1/+2
| | | | | | | | | | | Add testcase that executes all examples from taskflow/examples directory. For examples with somewhat deterministic output the output is also checked. This commit also fixes couple of examples broken by recent decorators refactoring. Change-Id: I3e65eabde43e1dd26b442d8f7dd3f062bf80703d
* Move examples under the source tree.Joshua Harlow2013-08-011-0/+50
The examples will likely be easier to find if they are colocated next to the rest of the source tree. They can also be turned into test cases in the future this way also. Change-Id: Iedcf5c51778459e5216b8072e71e271e7c7ee0bf
View Lorry Controller Status