@@ -12,7 +12,7 @@ an IOC.
1212.. literalinclude :: ../examples/example_asyncio_ioc.py
1313
1414
15- The ``dispatcher `` is created and passed to :func: `~softioc.softioc.iocInit `. This is what
15+ The ``dispatcher `` is created and passed to :func: `~softioc.softioc.iocInit `. This is what
1616allows the use of `asyncio ` functions in this IOC. It contains a new event loop to handle
1717this.
1818
@@ -21,13 +21,14 @@ sleeping that coroutine between updates.
2121Note that we run this coroutine in the ``loop `` of the ``dispatcher ``, and not in the
2222main event loop.
2323
24- This IOC will, like the one in `../tutorials/creating-an-ioc `, leave an interactive
25- shell open. The values of the PVs can be queried using the methods defined in the
24+ This IOC will, like the one in `../tutorials/creating-an-ioc `, leave an interactive
25+ shell open. The values of the PVs can be queried using the methods defined in the
2626`softioc.softioc ` module.
2727
2828
2929Asynchronous Channel Access
3030---------------------------
3131
32- PVs can be retrieved externally from a PV in an asynchronous manner by using the :py`aioca` module.
33- It provides ``await ``-able implementations of ``caget ``, ``caput ``, etc. See that module for more information.
32+ PVs can be retrieved externally from a PV in an asynchronous manner by using the
33+ `aioca ` module. It provides ``await ``-able implementations of ``caget ``,
34+ ``caput ``, etc. See that module for more information.
0 commit comments