> As for rthreads support, a quick search seems to indicate that its API is
> exactly the same as pthreads, and it's even binary compatible. Python will
> automatically use it when run on a OpenBSD system with rthreads enabled.

Well... not exactly. I asked on #openbsd:

22:07 < haypo> hi. what is the status of rthread? it looks like it is not 
available by default
22:14 < tp76> I might be wrong, but I don't think much work has been done on 
that in a while.
22:15 < haypo> tp76: i'm working on Python. Python is linked to pthread. I 
would like to know if we can link Python to rthread
22:16 < farhaven> no, you can't
22:17 < farhaven> rthreads is not (yet) a drop in replacement for pthreads and 
it basically works only if you use 
                  it for kernel threads
22:17 < farhaven> at least the manpage for rfork() advises against using it in 
userspace to create rthreads
22:18 < haypo> farhaven: does rthread have a userland API, similar to pthread, 
to manage threads?
22:18 < farhaven> nope, not that i know of
22:18 < haypo> i cannot find informations about rthread, only some old 
documents (2005)
22:18 < farhaven> afaik the only thing exposed to userland is rfork()'s 
RFTHREAD
22:19 < farhaven> i think tedu made a presentation about rthreads a while ago
22:19 < farhaven> but yeah, i wondered about that too one or two months ago
22:19 < farhaven> and it turned out, rthreads are not exactly usable :D

Your last patch is correct. Go ahead.