curio
curio copied to clipboard
Good Curio!
``` ================================================================================= FAILURES ================================================================================= _________________________________________________________________________________ test_cpu _________________________________________________________________________________ kernel = def test_cpu(kernel): results = [] async def spin(n): while n > 0: results.append(n) await sleep(0.1) n -= 1 async def cpu_bound(n):...
Importing curio in python 3.12 results in the following error: ```pytb In [1]: import curio --------------------------------------------------------------------------- AttributeError Traceback (most recent call last) Cell In[1], line 1 ----> 1 import curio...
Got this exception from inside curio/sched.py Not sure yet as to the cause. ``` Traceback (most recent call last): File "...", line 72, in curio.run(main) File "...\venv\Lib\site-packages\curio\kernel.py", line 824, in...
When running the test suite while packaging for openSUSE, I get this test failing: ``` [ 155s] =================================== FAILURES =================================== [ 155s] ______________________ test_worker_timeout[run_in_thread] ______________________ [ 155s] [ 155s] kernel...
I've noticed that the recommended way to write tests for curio programs is to use pytest and install the curio plugin. I prefer to just stick to the unittest library...
This merge request adds a TestCase class called CurioTestCase which mimics the IsolatedAsyncioTestCase available in the unittest library. With this it is enough to do `from curio.testcase import CurioTestCase` and...
Current curio's description is just [Curio](https://github.com/dabeaz/curio/blob/master/setup.py#L15). This is not very descriptive and I believe curio deserves more verbose description, for example `coroutine-based library for concurrent systems programming`.
```console + /usr/bin/python3 -Bm pytest -ra -q -k 'not internet' =========================================================================== test session starts ============================================================================ platform linux -- Python 3.8.9, pytest-6.2.4, py-1.10.0, pluggy-0.13.1 Using --randomly-seed=998889562 rootdir: /home/tkloczko/rpmbuild/BUILD/curio-1.5, configfile: setup.cfg, testpaths:...
Using ContextTask class currently creates empty context for each of the tasks. The desirable behavior would be that child tasks would have access to the parent task context. Right now...
Docs for size of queue [here](https://github.com/dabeaz/curio/blob/78bca8a6ad677ef51e1568ac7b3e51441ab49c42/docs/reference.rst#queues) suggest method `size()`, but in implementation [here](https://github.com/dabeaz/curio/blob/78bca8a6ad677ef51e1568ac7b3e51441ab49c42/curio/queue.py#L72) and [here](https://github.com/dabeaz/curio/blob/78bca8a6ad677ef51e1568ac7b3e51441ab49c42/curio/queue.py#L155) method is called `qsize()`