![](https://secure.gravatar.com/avatar/15b1cd41a4c23e7dc10893777afb4281.jpg?s=120&d=mm&r=g)
Hi, Le sam. 18 avr. 2020 à 19:16, Antoine Pitrou <solipsis@pitrou.net> a écrit :
Mostly, I hope that by making the subinterpreters functionality available to pure Python programmers (while it was formally an advanced and arcane part of the C API), we will spur of bunch of interesting third-party experimentations, including possibilities that we on python-dev have not thought about. (...) * I think the module should indeed be provisional. Experimentation may discover warts that call for a change in the API or semantics. Let's not prevent ourselves from fixing those issues.
Would it make sense to start by adding the module as a private "_subinterpreters" module but document it? The "_" prefix would be a reminder that "hey! it's experimental, there is a no backward compatibility warranty there". We can also add a big warning in the documentation. Victor