<story><title>500 Python Interpreters</title><url>https://izzys.casa/2024/08/463-python-interpreters/</url></story><parent_chain></parent_chain><comment><author>jiggunjer</author><text>So this means modules like concurrent.futures can create a thread pool object (as opposed to processpool) and run in parallel?&lt;p&gt;Or is the functionality as of 3.13 still limited to low level python embedding applications?</text></comment>
<story><title>500 Python Interpreters</title><url>https://izzys.casa/2024/08/463-python-interpreters/</url></story><parent_chain></parent_chain><comment><author>curious_cat_163</author><text>&amp;gt; &amp;quot;No matter what happens there is going to be a lock occurring. No two PyThreadStates can execute Python bytecode at the same time. However, they can execute multiple C calls at the same time which is why for long running pure C operations extension and embedding developers are encouraged to release the GIL temporarily.&amp;quot;&lt;p&gt;Very exciting!  I wonder what the first set of motivating applications are and what kind of performance gains are they expecting.</text></comment>