How uwsgi initialises python

uwsgi.md

1. This does all of the uWSGI initialization. It's a masterpiece of code cruft, but let's try to walk through it...

2. This initializes the python interpreters—creates and initializes the data structures for the interpreter, including one GIL for each worker.

3. By calling Python's API directly, not by shelling out!

You may also be interested to see when uWSGI does all the python environment setup, which includes importing files, creating the "uwsgi" module, etc. Note again that it does this by calling the python API directly, making the python interpreter part of its process

Here is the code that actually does the importing.

4. Finally, uWSGI spawns the workers. If you follow uwsgi_respawn_worker, you see that it's essentially just fork() ing. There's a separate interpreter instance for each worker.

5. But what about threads?

Threads are created as a new ThreadState within an existing interpreter, meaning they contend with GIL.