forked from M-Labs/artiq
1
0
Fork 0

style fixes

This commit is contained in:
Sebastien Bourdeauducq 2015-06-04 10:42:37 +08:00
parent 448ba042b5
commit 82a2beaa32
2 changed files with 4 additions and 4 deletions

View File

@ -18,7 +18,7 @@ def write_test_data(test_dict):
for key, value in enumerate(test_values): for key, value in enumerate(test_values):
test_dict[key] = value test_dict[key] = value
test_dict[1.5] = 1.5 test_dict[1.5] = 1.5
test_dict["Finished"] = True test_dict["finished"] = True
@asyncio.coroutine @asyncio.coroutine
@ -37,8 +37,8 @@ class SyncStructCase(unittest.TestCase):
return init return init
def notify(self, mod): def notify(self, mod):
if (mod["action"] == "init" and "Finished" in mod["struct"])\ if (mod["action"] == "init" and "finished" in mod["struct"])\
or (mod["action"] == "setitem" and mod["key"] == "Finished"): or (mod["action"] == "setitem" and mod["key"] == "finished"):
self.receiving_done.set() self.receiving_done.set()
def setUp(self): def setUp(self):

View File

@ -177,7 +177,7 @@ To flash the ``idle`` kernel:
* Compile the ``idle`` experiment: * Compile the ``idle`` experiment:
The ``idle`` experiment's ``run()`` method must be a kernel: it must be decorated with the ``@kernel`` decorator (see :ref:`next topic <connecting-to-the-core-device>` for more information about kernels). The ``idle`` experiment's ``run()`` method must be a kernel: it must be decorated with the ``@kernel`` decorator (see :ref:`next topic <connecting-to-the-core-device>` for more information about kernels).
Moreover, since the core device is not connected to the PC: RPC are forbidden in this ``idle`` experiment. Since the core device is not connected to the PC, RPCs (calling Python code running on the PC from the kernel) are forbidden in the ``idle`` experiment.
:: ::
$ artiq_compile idle.py $ artiq_compile idle.py