On 7 December 2017 at 01:50, Guido van Rossum
Sorry to burst your bubble, but I have not followed any of the discussion and I am actually very worried about this topic. I don't think I will be able to make time for this before the 3.7b1 feature freeze.
I think that will be OK, as it will encourage us to refactor Eric's branch into two distinct pieces in the meantime: exposing any needed C API elements that aren't currently visible as "nominally-private-but-linkable-if-you're-prepared-to-cope-with-potential-instability" interfaces, and then a pip-installable extension module that adds the Python level API. We won't be able to experiment with ideas like removing GIL sharing between subinterpreters that way, but we'll be able to work on the semantics of the user facing API design, and enable experimentation with things like CSP and Actor-based programming backed by stronger memory separation than is offered by Python threads. Cheers, Nick. -- Nick Coghlan | firstname.lastname@example.org | Brisbane, Australia