

Having horrible issues building blender currently, so have gone thru the motions of setting up virtual environments for freshly downloaded 2.91.2 and 2.92.0 usr/bin/virtualenv -p /usr/local/bin/python3.7 -always-copy fooĬreating a copy of the python to venv and from it blender runs without any extra steps required.

Thought I'd give the somewhat deprecated virtualenv a try, and bingo, blender ran straight up. Using /usr/local/bin/python3.7 -m venv foo -copies I ran into the no module named encodings error, and found no way to alleviate the situation. If having encodings hassles try virtualenvĪfter installing python 3.77 to /usr/local/ from a tarball, thought I would create a new python venv for blender. Any change I make, I know i am likely to break things, which hopefully would be only other addons, which will be ok (its all only a virtualenv that I can play around with, since i know the proper bundled one)Įdit. make Blender use this system python, of this virtualenv (if I have to issue a command like workon Blender2_91_2 before I start Blender, thats ok).make a virtualenv that corresponds exactly to that of the Blender bundled python + dependencies/modules.The workflow I am interested in woud look something like this: Prefferably, I would like to do this with virtualenv. What I cannot find is how to set up the system python to correspond perfectly with that of a given Blender version. Official information from Blender docs found here. Essentially: delete the python folder of the install, and Blender looks for a system version, where on some systems you need to supply the path yourself as: PYTHONPATH=/usr/lib/python3.7. I found lots of material on how to make Blender use the system version of python.
