I'm using a package that makes use of `threading.RLock` internally
The lock is used to prevent multiple threads from accessing an opened
filesystem, which makes sense. But I don't want it to do that for some
specific operations (I'm already ensuring operations are atomic).
So I am wondering if/how Nameko reacts to or is affected by
`threading.RLock` locks. Because if it isn't (my hope!) then I can
parallelize my operations by leveraging Nameko, rather than hacking
Thanks in advance for your help