Miguel Sánchez de León Peque
Miguel Sánchez de León Peque
To avoid some unnecessary waits or to improve assertions clarity.
A changelog file should be created starting on v1.0.0 to track future changes.
When using those patterns maybe it is interesting to repeat the request after the `wait` is exhausted for a number of times before executing the error handler.
Currently agents work as processes. It could be interesting to allow threaded agents as well, which share context with the parent agent and can, therefore, communicate with `inproc`.
Make all safe calls async (try to call `_loopback` to see how it currently blocks: second message to inproc never gets processed...). Depends on #30, #31.
Maybe we could use `._osbrain_xxx` instead of `._xxx`? We should probably do the same with hidden methods.
Like a one-way call, but is executed on a separate thread controlled by the Agent, and is stoppable. Agent keeps track of these tasks the same way it does with...
Decide which among them should be part of 0.8.0 release.
Should we set it to 1 for Unix socket files? (when using IPC transport) We should check if those socket files change their access time even when no messages are...
With Sphinx: ``` sphinx-build -E -W --color -b html -d {envtmpdir}/doctrees \ docs/source {envtmpdir}/html sphinx-build -E -W --color -b linkcheck -d {envtmpdir}/doctrees \ docs/source {envtmpdir}/linkcheck ``` Maybe `myint/rstcheck` and `PyCQA/pydocstyle`...