using python virtual environment for installation

[themighty1]

Today I again ran into issues building UI with make.
This time there was some kind of incompatibility between pyrcc5 and system-wide Qt.
I thought that maybe instead of chasing every time the library incompatibility issues and other corner cases, we could install all python dependencies using virtualenv.
We could pin each dependency to a certain version.

Any downsides to this approach?

[themighty1]

To be clear, I'm just suggesting that virtualenv approach is the default one in the wiki Compilation steps.

If somebody doesn't want virtualenv, he may simply skip those few step of creating a virtualenv.

My perception is that many may want to compile from source just want the added assurance that there is no foul play (as opposed to a binary file). People simply copy paste those compilation lines without caring/knowing what python virtualenv is.

So it is better to make the virtualenv option the default one rather than mention it as a possibility somewhere in the notes.