sascha/workload-automation
1
0
Fork 0
mirror of https://github.com/ARM-software/workload-automation.git synced 2025-09-02 11:22:41 +01:00
Code Issues Releases Wiki Activity

wa: Rename Instrumentation to Instruments

Browse Source 
To be maintain a consistent naming scheme, rename all instances of
`Instrumentation` to `Instruments`
This commit is contained in:
Marc Bonnici
2018-01-10 14:54:43 +00:00
committed by setrofim
parent 987f4ec4f1
commit 446a1cfbb0
23 changed files with 34 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
wa/framework/signal.py
View File

@@ -224,12 +224,12 @@ def connect(handler, signal, sender=dispatcher.Any, priority=0):
:handler: This can be any callable that that takes the right arguments for
the signal. For most signals this means a single argument that
will be an ``ExecutionContext`` instance. But please see documentation
for individual signals in the :ref:`signals reference <instrumentation_method_map>`.
for individual signals in the :ref:`signals reference <instruments_method_map>`.
:signal: The signal to which the handler will be subscribed. Please see
:ref:`signals reference <instrumentation_method_map>` for the list of standard WA
:ref:`signals reference <instruments_method_map>` for the list of standard WA
signals.
.. note:: There is nothing that prevents instrumentation from sending their
.. note:: There is nothing that prevents instruments from sending their
own signals that are not part of the standard set. However the signal
must always be an :class:`wa.core.signal.Signal` instance.
@@ -242,7 +242,7 @@ def connect(handler, signal, sender=dispatcher.Any, priority=0):
Defaults to 0.
.. note:: Priorities for some signals are inverted (so highest priority
handlers get executed last). Please see :ref:`signals reference <instrumentation_method_map>`
handlers get executed last). Please see :ref:`signals reference <instruments_method_map>`
for details.
"""