5ca61f956e
Most of the utility graph functions we have can be connected to a directed graph class that itself derives (and adds on to) the networkx base class. Doing this allows for functionality that isn't exposed in networkx to be exposed in our subclass (which is a useful pattern to have). It also makes it possible (if ever needed) to replace the networkx usage in taskflow with something else if this ever becomes a major request. Change-Id: I0a825d5637236d7b5dbdbda0d426adb0183d5ba3
25 lines
674 B
ReStructuredText
25 lines
674 B
ReStructuredText
-----
|
|
Utils
|
|
-----
|
|
|
|
There are various helper utils that are part of taskflows internal usage (and
|
|
external/public usage of these helpers should be kept to a minimum as these
|
|
utility functions may be altered more often in the future).
|
|
|
|
External usage
|
|
==============
|
|
|
|
The following classes and modules are *recommended* for external usage:
|
|
|
|
.. autoclass:: taskflow.utils.misc.Failure
|
|
:members:
|
|
|
|
.. autoclass:: taskflow.utils.eventlet_utils.GreenExecutor
|
|
:members:
|
|
|
|
.. autofunction:: taskflow.utils.persistence_utils.temporary_log_book
|
|
|
|
.. autofunction:: taskflow.utils.persistence_utils.temporary_flow_detail
|
|
|
|
.. autofunction:: taskflow.utils.persistence_utils.pformat
|