On 26 Sep 2017, at 17:11, Billy Poon <[email protected]> wrote:

I just chatted with Tristan Croll from Cambridge at the Phenix developer workshop. Would the Global Interpreter Lock be an issue?

https://docs.python.org/2.7/c-api/init.html#thread-state-and-the-global-interpreter-lock

It sounds like we should be releasing the lock before doing any threading and then reacquiring the lock afterwards.

So that means you plan your threaded code to call back into Python, then? This would be quite unusual in the context of the cctbx but I haven’t followed development closely for a long while, so I might have missed something.

Best wishes,

Luc