I would always recommend to take the virtualenv approach for non-trivial python software. The same principle is used for e.g. WARs or take a look at docker-compose, they even bundle Python itself. Wasting 30MB disk space is nothing compared to the effort needed to align every Python software on an OS in regards of their dependencies.
I would always recommend to take the virtualenv approach for non-trivial python
software.
In this particular case it's not a matter of whether to use virtualenv or not or whether
disk space is wasted. The real issue is the need for version pinning which eventually
leads to missing important security updates.
The same principle is used for e.g. WARs or take a look at docker-compose, they even
bundle Python itself. Wasting 30MB disk space is nothing compared to the effort needed
to align every Python software on an OS in regards of their dependencies.
Yes, but same issues with how to install security updates there.