summaryrefslogtreecommitdiff
path: root/taskflow/examples/wbe_simple_linear.py
Commit message (Collapse)AuthorAgeFilesLines
* When creating daemon threads use the bundled threading_utilsJoshua Harlow2014-11-191-3/+2
| | | | | | | | | | | Instead of creating daemon threads using the threads module directly use our small utility file to create the daemon thread on our behalf and set the appropriate attributes to ensure it's a daemon thread. This change replaces the existing locations where we were doing this manually and uses the threading_utils helper function uniformly instead. Change-Id: I535cee8a63407f753cf812df53c4f5bc83e0c9ae
* Deprecate `engine_conf` and prefer `engine` insteadJoshua Harlow2014-10-181-9/+5
| | | | | | | | | | | | | | | | | | | | | | To avoid having one set of options coming from `engine_conf` and another set of options coming from `kwargs` and another set coming from `engine_conf` if it is a URI just start to shift toward `engine_conf` being deprecated and `engine` being a string type only (or a URI with additional query parameters) and having any additional **kwargs that are provided just get merged into the final engine options. This adds a new helper function that handles all these various options and adds in a keyword argument `engine` that will be shifted to in a future version (in that future version we can also then remove the `engine_conf` and just stick to a smaller set of option mechanisms). It also adjusts all examples to use this new and more easier to understand format and adjusts tests, conductor interface to use this new more easily understandable style of getting an engine. Change-Id: Ic7617057338e0c63775cf38a24643cff6e454950
* Mention issue with more than one thread and reduce workersJoshua Harlow2014-09-121-3/+10
| | | | | | | | | | | | | | Due to how it appears the filesystem transport in kombu is not thread-safe we will work around this by not having more than one worker active at the same time in this example. Oddly it appears the memory transport is unaffected (but from looking at the code it doesn't look safe either), this may just be due to how the python memory model works though. Part of blueprint more-examples Change-Id: Idaf04fb1a6a622af292511bbcf25329c9a5aab53
* Cleanup WBE example to be simpler to understandJoshua Harlow2014-08-301-0/+146
This makes the example simpler to follow and understand when it is using threads, is in one file and just uses the simpler in-memory kombu backend by default (it can still use the file transport if configured to use it). Change-Id: I7fe9758e3285e7f0a610482bf26322841fb22f39