delta/openstack/taskflow.git/taskflow/examples/dump_memory_backend.py, branch master opendev.org: openstack/taskflow.git Remove **most** usage of taskflow.utils in examples 2015-07-17T15:48:17+00:00 Joshua Harlow harlowja@yahoo-inc.com 2015-07-13T18:33:12+00:00 02c83d40612bbe3146a9f2ff212759ecdcdeb8ba It appears folks are using the taskflow.utils code in there own code-bases (likely taking it from the examples) which we do not want to encourage, so remove the usage of **most** of taskflow.utils code from the examples so that people are less likely to copy/paste/reference it. Change-Id: I0ce3c520de347e3e746e7912aa1366a515458424 
It appears folks are using the taskflow.utils code in there own
code-bases (likely taking it from the examples) which we do not
want to encourage, so remove the usage of **most** of
taskflow.utils code from the examples so that people are less
likely to copy/paste/reference it.

Change-Id: I0ce3c520de347e3e746e7912aa1366a515458424
Add a new `ls_r` method 2015-06-04T17:39:20+00:00 Joshua Harlow harlowja@yahoo-inc.com 2015-05-14T20:04:24+00:00 4ee5ffd0871fcab8e814c0eaade0f184570269b1 Instead of having a `ls` method that when used recursively *always* returns the absolute path of items in the fake in memory storage tree and *relative* paths (when used in non-recursive mode) add a new `ls_r` method that can return absolute *or* relative paths. In the future it is highly likely that the the `ls` recursive keyword argument will be removed (so preferring and moving to the `ls_r` should occur earlier rather than later), so this also adds a debtcollector removed keyword argument decorator over the existing `ls` to ensure that users are aware of this change (as well as a adjusted docstring). Fixes bug 1458114 Change-Id: Id2a5869e94ac44679020a14297d1073d1dc2718f 
Instead of having a `ls` method that when used recursively
*always* returns the absolute path of items in the fake in
memory storage tree and *relative* paths (when used in
non-recursive mode) add a new `ls_r` method that can return
absolute *or* relative paths.

In the future it is highly likely that the the `ls` recursive
keyword argument will be removed (so preferring and
moving to the `ls_r` should occur earlier rather than
later), so this also adds a debtcollector removed keyword
argument decorator over the existing `ls` to ensure that users
are aware of this change (as well as a adjusted docstring).

Fixes bug 1458114

Change-Id: Id2a5869e94ac44679020a14297d1073d1dc2718f
Allow ls() to list recursively (using breadth-first) 2015-03-31T18:43:55+00:00 Joshua Harlow harlowja@yahoo-inc.com 2015-03-24T18:39:42+00:00 ce7b1d2c92e901f213f71c4c3e4d9c5f2145ff70 Make it easier to list the contents of the full in-memory filesystem by allowing the ls() function to take a recursive keyword argument (which by default is false). This makes it easier to analyze the contents of the full in memory filesystem; saving people from creating similar code themselves. Change-Id: I573797945255cb81728e7a86b58768b848110ee7 
Make it easier to list the contents of the full in-memory
filesystem by allowing the ls() function to take a recursive
keyword argument (which by default is false).

This makes it easier to analyze the contents of the full in
memory filesystem; saving people from creating similar code
themselves.

Change-Id: I573797945255cb81728e7a86b58768b848110ee7
Add a in-memory backend dumping example 2015-03-12T19:41:44+00:00 Joshua Harlow harlowja@yahoo-inc.com 2015-03-12T00:45:31+00:00 86021183570a26361cd4ba2fd9536ca713c14ebe Change-Id: Ie29735a16129cedd574e09ed06b44a98560f0d90 
Change-Id: Ie29735a16129cedd574e09ed06b44a98560f0d90