How to run uwsgi with different virtualenv

[SISalp (Dominique Chabord)]

This answer refers Multiple instances with VENV, nginx, uwsgi, sao, certbot - #5 by herrdeh but addresses the same topic.

@herrdeh

So, our assumption was that a system-wide uwsgi would improve performance; on the other side we have flexibility to run different version and module sets in VENVs.

Using an alternative to Werkzeug in production is a recommendation (from werkzeug), indeed.

Now this is my understanding (please community, correct me):

You don’t need virtualenvs to run different copies of trytond, sao, proteus. Start them directly from code copy. They will all run in the same system wide environment which must be compatible with all servers.

I use virtualenvs to set dependencies specifically according to each trytond service requirements. Specific python3 versions in particular.

I made the assumption that uswgi and its python3 extension are python-version sensitive. This is how I explain that pip install requires recompilation, depending on the python version used in the environment.
Therefore, I doubt a system-wide uwsgi can serve different virtualenvs if they differ by their python version. (but again, Lukio seemed affirmative in How to run trytond with nginx + supervisord + uwsgi)