Cody Piersall

This can be done now as a side effect of passing `-d yes`: ```console root@microzed-zynq7 ~ ./unittests -d yes 0.000 s: Can instantiate Thing 0.000 s: Structs are the right...

> What you should do is probably set a flag to wake up a thread in your user program that just closes the socket in question. The problem is that...

I ran into this blog post by Martin Sustrik about EINTR: http://250bpm.com/blog:12 It mentions that pyzmq used to act like pynng is acting now, but it looks like zmq started...

Okay, on Windows it turns out that [pyzmq](https://github.com/zeromq/pyzmq) and the [legacy nanomsg bindings](https://github.com/tonysimpson/nanomsg-python) do the same thing as pynng, but that is just due to how Windows and POSIX differ...

A little spelunking in libzmq's git history reveals that `EINTR` was allowed to percolate to callers in commit https://github.com/zeromq/libzmq/commit/91ea20464439b5359a5. Additionally, and more importantly, it turns out that it is not...

> Sounds like this is a bug in python then. I think it was a design decision more than a bug, maybe due to some limitations of the Python VM....

Sorry, I think my last post was a bit stream-of-consciousness. Unfortunately, the Python runtime will never actually call any installed signal handlers when a blocking call is made in pynng,...

> What I'd propose then is to have some special property on the socket that disables restart of an interrupted system call. NNG_NORESTART. Ah yeah, a socket option seems like...

> Going back and looking at this, I want to punch Python in the nose. Again. :joy: > Did you want to try to put together a PR, or should...

On Linux, `&` runs the command in the background. On Windows, the equivalent is here: https://superuser.com/questions/198525/how-can-i-execute-a-windows-command-line-in-background `start /b pipeline node0 ...` etc. I think :-)