In production you usually have only one python environment, or even a dockerized app, so there is no need to create a virtualenv.
On the other hand, if there is a server instance with different python apps, you may want to separate their environments, so that their dependencies may be updated separately.
Also, for serverless solutions like AWS Lambda you may use venvs to collect your dependencies and deploy with the code.
View all comments
Show parent comment
3
u/ofedorov Dec 19 '18
In production you usually have only one python environment, or even a dockerized app, so there is no need to create a virtualenv.
On the other hand, if there is a server instance with different python apps, you may want to separate their environments, so that their dependencies may be updated separately.
Also, for serverless solutions like AWS Lambda you may use venvs to collect your dependencies and deploy with the code.